Beam Failure Recovery In A Power Saving Operation

ABSTRACT

Wireless communication techniques for power saving are described. A wireless device may be configured with one or more power saving configurations, such as a dormant state. During a dormant state, downlink channel monitoring (e.g., on a secondary cell) may be stopped and/or a beam failure recovery procedure may be performed.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of and claims priority to U.S. patentapplication Ser. No. 16/577,847, filed Sep. 20, 2019, which claims thebenefit of U.S. Provisional Application No. 62/734,561, filed on Sep.21, 2018, and U.S. Provisional Application No. 62/790,306, filed Jan. 9,2019. Each of the above-referenced applications is hereby incorporatedby reference in its entirety.

BACKGROUND

Wireless communication protocols may use power saving mechanisms forpower conservation. A device and/or a system may switch between a powersaving mode and an active mode for different types of services.Switching between different modes may require additional consumption ofresources (e.g., frequency resources, time resources, energy resources)at the communication device. This may lead system inefficiencies.

SUMMARY

The following summary presents a simplified summary of certain features.The summary is not an extensive overview and is not intended to identifykey or critical elements.

A first communication device (e.g., a wireless device) may switchbetween an active state (e.g., active mode) and one or more power savingstates (e.g., power saving mode). The first communication device mayswitch between the different power saving states and/or the activestate, for example, based on data service and/or data traffic. The firstcommunication device may receive, from a second communication device(e.g., a base station), one or more first messages comprising one ormore power saving configurations. The first communication device mayreceive, from the second communication device, a second messageindicating a power saving configuration of the one or more power savingconfigurations. Based on receiving the second message, the firstcommunication device may switch between an active state to a powersaving state and/or monitor a power saving channel in the power savingmode. The first communication device may receive (e.g., from the secondcommunication device) a wake-up indication via the power saving channel.Using the second message to indicate a switch to the power saving statemay improve resource utilization in a communication system.

BRIEF DESCRIPTION OF THE DRAWINGS

Some features are shown by way of example, and not by limitation, in theaccompanying drawings. In the drawings, like numerals reference similarelements.

FIG. 1 shows an example radio access network (RAN) architecture.

FIG. 2A shows an example user plane protocol stack.

FIG. 2B shows an example control plane protocol stack.

FIG. 3 shows an example wireless device and two base stations.

FIG. 4A, FIG. 4B, FIG. 4C, and FIG. 4D show examples of uplink anddownlink signal transmission.

FIG. 5A shows an example uplink channel mapping and example uplinkphysical signals.

FIG. 5B shows an example downlink channel mapping and example downlinkphysical signals.

FIG. 6 shows an example transmission time and/or reception time for acarrier.

FIG. 7A and FIG. 7B show example sets of orthogonal frequency divisionmultiplexing (OFDM) subcarriers.

FIG. 8 shows example OFDM radio resources.

FIG. 9A shows an example channel state information reference signal(CSI-RS) and/or synchronization signal (SS) block transmission in amulti-beam system.

FIG. 9B shows an example downlink beam management procedure.

FIG. 10 shows an example of configured bandwidth parts (BWPs).

FIG. 11A and FIG. 11B show examples of multi connectivity.

FIG. 12 shows an example of a random access procedure.

FIG. 13 shows example medium access control (MAC) entities.

FIG. 14 shows an example RAN architecture.

FIG. 15 shows example radio resource control (RRC) states.

FIG. 16A, FIG. 16B and FIG. 16C show examples of MAC subheaders.

FIG. 17A and FIG. 17B show examples of MAC PDUs.

FIG. 18 shows an example of LCIDs for DL-SCH.

FIG. 19 shows an example of LCIDs for UL-SCH.

FIG. 20A and FIG. 20B show examples of secondary cell (SCell)Activation/Deactivation MAC CE.

FIG. 21A shows an example of an SCell hibernation MAC control element(CE).

FIG. 21B shows an example of an SCell hibernation MAC CE.

FIG. 21C shows an example of MAC CEs for SCell state transitions.

FIG. 22 shows an example for SCell state transition.

FIG. 23 shows an example for SCell state transition.

FIG. 24 shows an example of BWP switching for an SCell.

FIG. 25 shows an example of discontinuous reception (DRX) operation.

FIG. 26 shows an example of DRX operation.

FIG. 27A shows an example of a wake-up signal/channel based power savingoperation.

FIG. 27B shows an example of a go-to-sleep signal/channel based powersaving operation.

FIG. 28 shows an example of activation/deactivation of a power savingoperation.

FIG. 29 shows an example of activation/deactivation of a power savingoperation.

FIG. 30 shows an example of activation/deactivation of a power savingoperation.

FIG. 31 shows an example of activation/deactivation of a power savingoperation.

FIG. 32 shows an example of a power saving operation.

FIG. 33 shows an example method of a power saving operation.

FIG. 34 shows an example of method of a power saving operation.

FIG. 35 shows an example of CSI RS transmission with multiple beams.

FIG. 36 shows an example of various beam management procedures.

FIG. 37A and FIG. 37B show examples of beam failure.

FIG. 38 shows an example of a beam failure recovery procedure.

FIG. 39 shows an example of DCI formats.

FIG. 40 shows an example diagram of a power saving mode.

FIG. 41 shows an example diagram of a power saving mode.

FIG. 42 shows an example diagram of a DRX-based power saving mode.

FIG. 43 shows an example diagram of beam failure recovery in powersaving mode.

FIG. 44 shows an example diagram of beam failure recovery in powersaving mode.

FIG. 45 shows an example diagram of beam failure recovery in powersaving mode.

FIG. 46 shows an example diagram of beam failure recovery in powersaving mode.

FIG. 47 shows an example diagram of beam failure recovery in powersaving mode.

FIG. 48 shows an example diagram of beam failure recovery in powersaving mode.

FIG. 49 shows an example diagram of beam failure recovery in powersaving mode.

FIG. 50 shows an example diagram of beam failure recovery in powersaving mode.

FIG. 51 shows an example diagram of beam failure recovery in powersaving mode.

FIG. 52 shows example elements of a computing device that may be used toimplement any of the various devices described herein.

DETAILED DESCRIPTION

The accompanying drawings and descriptions provide examples. It is to beunderstood that the examples shown in the drawings and/or described arenon-exclusive and that there are other examples of how features shownand described may be practiced.

Examples are provided for operation of wireless communication systemswhich may be used in the technical field of multicarrier communicationsystems. More particularly, the technology described herein may relateto resource management for wireless communications.

The following acronyms are used throughout the drawings and/ordescriptions, and are provided below for convenience although otheracronyms may be introduced in the detailed description:

3GPP 3rd Generation Partnership Project 5GC 5G Core Network ACKAcknowledgement AMF Access and Mobility Management Function ARQAutomatic Repeat Request AS Access Stratum ASIC Application-SpecificIntegrated Circuit BA Bandwidth Adaptation BCCH Broadcast ControlChannel BCH Broadcast Channel BPSK Binary Phase Shift Keying BWPBandwidth Part CA Carrier Aggregation CC Component Carrier CCCH CommonControl CHannel CDMA Code Division Multiple Access CE Control Element CNCore Network CORESET Control Resource Set CP Cyclic Prefix CP-OFDMCyclic Prefix-Orthogonal Frequency Division Multiplex C-RNTI Cell-RadioNetwork Temporary Identifier CS Configured Scheduling CSI Channel StateInformation CSI-RS Channel State Information-Reference Signal CQIChannel Quality Indicator

CRI CSI-RS resource indicator

CSS Common Search Space CU Central Unit DC Dual Connectivity DCCHDedicated Control Channel DCI Downlink Control Information DL DownlinkDL-SCH Downlink Shared CHannel DM-RS DeModulation Reference Signal DRBData Radio Bearer DRX Discontinuous Reception DTCH Dedicated TrafficChannel DU Distributed Unit EPC Evolved Packet Core E-UTRA Evolved UMTSTerrestrial Radio Access E-UTRAN Evolved-Universal Terrestrial RadioAccess Network FDD Frequency Division Duplex FPGA Field ProgrammableGate Arrays

F1-C F1-Control planeF1-U F1-User planegNB next generation Node BHARQ Hybrid Automatic Repeat reQuest

HDL Hardware Description Languages IE Information Element IP InternetProtocol LCID Logical Channel Identifier LI Layer Indicator LTE LongTerm Evolution MAC Medium Access Control MCG Master Cell Group MCSModulation and Coding Scheme

MeNB Master evolved Node B

MIB Master Information Block MME Mobility Management Entity MN MasterNode j NACK Negative Acknowledgement NAS Non-Access Stratum NG CP NextGeneration Control Plane NGC Next Generation Core

NG-C NG-Control planeng-eNB next generation evolved Node BNG-U NG-User plane

NR New Radio NR MAC New Radio MAC NR PDCP New Radio PDCP NR PHY NewRadio PHYsical NR RLC New Radio RLC NR RRC New Radio RRC NSSAI NetworkSlice Selection Assistance Information O&M Operation and MaintenanceOFDM Orthogonal Frequency Division Multiplexing PBCH Physical BroadcastCHannel PCC Primary Component Carrier PCCH Paging Control CHannel PCellPrimary Cell PCH Paging CHannel PDCCH Physical Downlink Control CHannelPDCP Packet Data Convergence Protocol PDSCH Physical Downlink SharedCHannel PDU Protocol Data Unit PHICH Physical HARQ Indicator CHannel PHYPHYsical PLMN Public Land Mobile Network PMI Precoding Matrix IndicatorPRACH Physical Random Access CHannel PRB Physical Resource Block PSCellPrimary Secondary Cell PSS Primary Synchronization Signal

pTAG primary Timing Advance Group

PT-RS Phase Tracking Reference Signal PUCCH Physical Uplink ControlCHannel PUSCH Physical Uplink Shared CHannel QAM Quadrature AmplitudeModulation QCLed Quasi-Co-Located QCL Quasi-Co-Location QFI Quality ofService Indicator QoS Quality of Service QPSK Quadrature Phase ShiftKeying RA Random Access RACH Random Access CHannel RAN Radio AccessNetwork RAT Radio Access Technology RA-RNTI Random Access-Radio NetworkTemporary Identifier RB Resource Blocks RBG Resource Block Groups

RI Rank indicator

RLC Radio Link Control RLM Radio Link Monitoring RNTI Radio NetworkTemporary Identifier RRC Radio Resource Control RRM Radio ResourceManagement RS Reference Signal RSRP Reference Signal Received Power SCCSecondary Component Carrier SCell Secondary Cell SCG Secondary CellGroup SC-FDMA Single Carrier-Frequency Division Multiple Access SDAPService Data Adaptation Protocol SDU Service Data Unit

SeNB Secondary evolved Node B

SFN System Frame Number S-GW Serving GateWay SI System Information SIBSystem Information Block SINR Signal-to-Interference-plus-Noise RatioSMF Session Management Function SN Secondary Node SpCell Special CellSRB Signaling Radio Bearer SRS Sounding Reference Signal SSSynchronization Signal SSB Synchronization Signal Block SSBRISynchronization Signal Block Resource Indicator SSS SecondarySynchronization Signal

sTAG secondary Timing Advance Group

TA Timing Advance TAG Timing Advance Group TAI Tracking Area IdentifierTAT Time Alignment Timer TB Transport Block TC-RNTI Temporary Cell-RadioNetwork Temporary Identifier TCI Transmission Configuration IndicationTDD Time Division Duplex TDMA Time Division Multiple Access TRPTransmission Reception Point TTI Transmission Time Interval UCI UplinkControl Information UE User Equipment UL Uplink UL-SCH Uplink SharedCHannel UPF User Plane Function UPGW User Plane Gateway URLLCUltra-Reliable Low-Latency Communication

V2X Vehicle-to-everything

VHDL VHSIC Hardware Description Language

Xn-C Xn-Control planeXn-U Xn-User plane

Examples described herein may be implemented using various physicallayer modulation and transmission mechanisms. Example transmissionmechanisms may include, but are not limited to: Code Division MultipleAccess (CDMA), Orthogonal Frequency Division Multiple Access (OFDMA),Time Division Multiple Access (TDMA), Wavelet technologies, and/or thelike. Hybrid transmission mechanisms such as TDMA/CDMA, and/or OFDM/CDMAmay be used. Various modulation schemes may be used for signaltransmission in the physical layer. Examples of modulation schemesinclude, but are not limited to: phase, amplitude, code, a combinationof these, and/or the like. An example radio transmission method mayimplement Quadrature Amplitude Modulation (QAM) using Binary Phase ShiftKeying (BPSK), Quadrature Phase Shift Keying (QPSK), 16-QAM, 64-QAM,256-QAM, 1024-QAM and/or the like. Physical radio transmission may beenhanced by dynamically or semi-dynamically changing the modulation andcoding scheme, for example, depending on transmission requirementsand/or radio conditions.

FIG. 1 shows an example Radio Access Network (RAN) architecture. A RANnode may comprise a next generation Node B (gNB) (e.g., 120A, 120B)providing New Radio (NR) user plane and control plane protocolterminations towards a first wireless device (e.g., 110A). A RAN nodemay comprise a base station such as a next generation evolved Node B(ng-eNB) (e.g., 120C, 120D), providing Evolved UMTS Terrestrial RadioAccess (E-UTRA) user plane and control plane protocol terminationstowards a second wireless device (e.g., 110B). A first wireless device110A may communicate with a base station, such as a gNB 120A, over a Uuinterface. A second wireless device 110B may communicate with a basestation, such as an ng-eNB 120D, over a Uu interface. The wirelessdevices 110A and/or 110B may be structurally similar to wireless devicesshown in and/or described in connection with other drawing figures. TheNode B 120A, the Node B 120B, the Node B 120C, and/or the Node B 120Dmay be structurally similar to Nodes B and/or base stations shown inand/or described in connection with other drawing figures.

A base station, such as a gNB (e.g., 120A, 120B, etc.) and/or an ng-eNB(e.g., 120C, 120D, etc.) may host functions such as radio resourcemanagement and scheduling, IP header compression, encryption andintegrity protection of data, selection of Access and MobilityManagement Function (AMF) at wireless device (e.g., User Equipment (UE))attachment, routing of user plane and control plane data, connectionsetup and release, scheduling and transmission of paging messages (e.g.,originated from the AMF), scheduling and transmission of systembroadcast information (e.g., originated from the AMF or Operation andMaintenance (O&M)), measurement and measurement reporting configuration,transport level packet marking in the uplink, session management,support of network slicing, Quality of Service (QoS) flow management andmapping to data radio bearers, support of wireless devices in aninactive state (e.g., RRC_INACTIVE state), distribution function forNon-Access Stratum (NAS) messages, RAN sharing, dual connectivity,and/or tight interworking between NR and E-UTRA.

One or more first base stations (e.g., gNBs 120A and 120B) and/or one ormore second base stations (e.g., ng-eNBs 120C and 120D) may beinterconnected with each other via Xn interface. A first base station(e.g., gNB 120A, 120B, etc.) or a second base station (e.g., ng-eNB120C, 120D, etc.) may be connected via NG interfaces to a network, suchas a 5G Core Network (5GC). A 5GC may comprise one or more AMF/User PlanFunction (UPF) functions (e.g., 130A and/or 130B). A base station (e.g.,a gNB and/or an ng-eNB) may be connected to a UPF via an NG-User plane(NG-U) interface. The NG-U interface may provide delivery (e.g.,non-guaranteed delivery) of user plane Protocol Data Units (PDUs)between a RAN node and the UPF. A base station (e.g., a gNB and/or anng-eNB) may be connected to an AMF via an NG-Control plane (NG-C)interface. The NG-C interface may provide functions such as NG interfacemanagement, wireless device (e.g., UE) context management, wirelessdevice (e.g., UE) mobility management, transport of NAS messages,paging, PDU session management, configuration transfer, and/or warningmessage transmission.

A UPF may host functions such as anchor point for intra-/inter-RadioAccess Technology (RAT) mobility (e.g., if applicable), external PDUsession point of interconnect to data network, packet routing andforwarding, packet inspection and user plane part of policy ruleenforcement, traffic usage reporting, uplink classifier to supportrouting traffic flows to a data network, branching point to supportmulti-homed PDU session, quality of service (QoS) handling for userplane, packet filtering, gating, Uplink (UL)/Downlink (DL) rateenforcement, uplink traffic verification (e.g., Service Data Flow (SDF)to QoS flow mapping), downlink packet buffering, and/or downlink datanotification triggering.

An AMF may host functions such as NAS signaling termination, NASsignaling security, Access Stratum (AS) security control, inter CoreNetwork (CN) node signaling (e.g., for mobility between 3rd GenerationPartnership Project (3GPP) access networks), idle mode wireless devicereachability (e.g., control and execution of paging retransmission),registration area management, support of intra-system and inter-systemmobility, access authentication, access authorization including check ofroaming rights, mobility management control (e.g., subscription and/orpolicies), support of network slicing, and/or Session ManagementFunction (SMF) selection.

FIG. 2A shows an example user plane protocol stack. A Service DataAdaptation Protocol (SDAP) (e.g., 211 and 221), Packet Data ConvergenceProtocol (PDCP) (e.g., 212 and 222), Radio Link Control (RLC) (e.g., 213and 223), and Medium Access Control (MAC) (e.g., 214 and 224) sublayers,and a Physical (PHY) (e.g., 215 and 225) layer, may be terminated in awireless device (e.g., 110) and in a base station (e.g., 120) on anetwork side. A PHY layer may provide transport services to higherlayers (e.g., MAC, RRC, etc.). Services and/or functions of a MACsublayer may comprise mapping between logical channels and transportchannels, multiplexing and/or demultiplexing of MAC Service Data Units(SDUs) belonging to the same or different logical channels into and/orfrom Transport Blocks (TBs) delivered to and/or from the PHY layer,scheduling information reporting, error correction through HybridAutomatic Repeat request (HARQ) (e.g., one HARQ entity per carrier forCarrier Aggregation (CA)), priority handling between wireless devicessuch as by using dynamic scheduling, priority handling between logicalchannels of a wireless device such as by using logical channelprioritization, and/or padding. A MAC entity may support one or multiplenumerologies and/or transmission timings. Mapping restrictions in alogical channel prioritization may control which numerology and/ortransmission timing a logical channel may use. An RLC sublayer maysupport transparent mode (TM), unacknowledged mode (UM), and/oracknowledged mode (AM) transmission modes. The RLC configuration may beper logical channel with no dependency on numerologies and/orTransmission Time Interval (TTI) durations. Automatic Repeat Request(ARQ) may operate on any of the numerologies and/or TTI durations withwhich the logical channel is configured. Services and functions of thePDCP layer for the user plane may comprise, for example, sequencenumbering, header compression and decompression, transfer of user data,reordering and duplicate detection, PDCP PDU routing (e.g., such as forsplit bearers), retransmission of PDCP SDUs, ciphering, deciphering andintegrity protection, PDCP SDU discard, PDCP re-establishment and datarecovery for RLC AM, and/or duplication of PDCP PDUs. Services and/orfunctions of SDAP may comprise, for example, mapping between a QoS flowand a data radio bearer. Services and/or functions of SDAP may comprisemapping a Quality of Service Indicator (QFI) in DL and UL packets. Aprotocol entity of SDAP may be configured for an individual PDU session.

FIG. 2B shows an example control plane protocol stack. A PDCP (e.g., 233and 242), RLC (e.g., 234 and 243), and MAC (e.g., 235 and 244)sublayers, and a PHY (e.g., 236 and 245) layer, may be terminated in awireless device (e.g., 110), and in a base station (e.g., 120) on anetwork side, and perform service and/or functions described above. RRC(e.g., 232 and 241) may be terminated in a wireless device and a basestation on a network side. Services and/or functions of RRC may comprisebroadcast of system information related to AS and/or NAS; paging (e.g.,initiated by a 5GC or a RAN); establishment, maintenance, and/or releaseof an RRC connection between the wireless device and RAN; securityfunctions such as key management, establishment, configuration,maintenance, and/or release of Signaling Radio Bearers (SRBs) and DataRadio Bearers (DRBs); mobility functions; QoS management functions;wireless device measurement reporting and control of the reporting;detection of and recovery from radio link failure; and/or NAS messagetransfer to/from NAS from/to a wireless device. NAS control protocol(e.g., 231 and 251) may be terminated in the wireless device and AMF(e.g., 130) on a network side. NAS control protocol may performfunctions such as authentication, mobility management between a wirelessdevice and an AMF (e.g., for 3GPP access and non-3GPP access), and/orsession management between a wireless device and an SMF (e.g., for 3GPPaccess and non-3GPP access).

A base station may configure a plurality of logical channels for awireless device. A logical channel of the plurality of logical channelsmay correspond to a radio bearer. The radio bearer may be associatedwith a QoS requirement. A base station may configure a logical channelto be mapped to one or more TTIs and/or numerologies in a plurality ofTTIs and/or numerologies. The wireless device may receive DownlinkControl Information (DCI) via a Physical Downlink Control CHannel(PDCCH) indicating an uplink grant. The uplink grant may be for a firstTTI and/or a first numerology and may indicate uplink resources fortransmission of a transport block. The base station may configure eachlogical channel in the plurality of logical channels with one or moreparameters to be used by a logical channel prioritization procedure atthe MAC layer of the wireless device. The one or more parameters maycomprise, for example, priority, prioritized bit rate, etc. A logicalchannel in the plurality of logical channels may correspond to one ormore buffers comprising data associated with the logical channel. Thelogical channel prioritization procedure may allocate the uplinkresources to one or more first logical channels in the plurality oflogical channels and/or to one or more MAC Control Elements (CEs). Theone or more first logical channels may be mapped to the first TTI and/orthe first numerology. The MAC layer at the wireless device may multiplexone or more MAC CEs and/or one or more MAC SDUs (e.g., logical channel)in a MAC PDU (e.g., transport block). The MAC PDU may comprise a MACheader comprising a plurality of MAC sub-headers. A MAC sub-header inthe plurality of MAC sub-headers may correspond to a MAC CE or a MAC SUD(e.g., logical channel) in the one or more MAC CEs and/or in the one ormore MAC SDUs. A MAC CE and/or a logical channel may be configured witha Logical Channel IDentifier (LCID). An LCID for a logical channeland/or a MAC CE may be fixed and/or pre-configured. An LCID for alogical channel and/or MAC CE may be configured for the wireless deviceby the base station. The MAC sub-header corresponding to a MAC CE and/ora MAC SDU may comprise an LCID associated with the MAC CE and/or the MACSDU.

A base station may activate, deactivate, and/or impact one or moreprocesses (e.g., set values of one or more parameters of the one or moreprocesses or start and/or stop one or more timers of the one or moreprocesses) at the wireless device, for example, by using one or more MACcommands. The one or more MAC commands may comprise one or more MACcontrol elements. The one or more processes may comprise activationand/or deactivation of PDCP packet duplication for one or more radiobearers. The base station may send (e.g., transmit) a MAC CE comprisingone or more fields. The values of the fields may indicate activationand/or deactivation of PDCP duplication for the one or more radiobearers. The one or more processes may comprise Channel StateInformation (CSI) transmission of on one or more cells. The base stationmay send (e.g., transmit) one or more MAC CEs indicating activationand/or deactivation of the CSI transmission on the one or more cells.The one or more processes may comprise activation and/or deactivation ofone or more secondary cells. The base station may send (e.g., transmit)a MAC CE indicating activation and/or deactivation of one or moresecondary cells. The base station may send (e.g., transmit) one or moreMAC CEs indicating starting and/or stopping of one or more DiscontinuousReception (DRX) timers at the wireless device. The base station may send(e.g., transmit) one or more MAC CEs indicating one or more timingadvance values for one or more Timing Advance Groups (TAGs).

FIG. 3 shows an example of base stations (base station 1, 120A, and basestation 2, 120B) and a wireless device 110. The wireless device 110 maycomprise a UE or any other wireless device. The base station (e.g.,120A, 120B) may comprise a Node B, eNB, gNB, ng-eNB, or any other basestation. A wireless device and/or a base station may perform one or morefunctions of a relay node. The base station 1, 120A, may comprise atleast one communication interface 320A (e.g., a wireless modem, anantenna, a wired modem, and/or the like), at least one processor 321A,and at least one set of program code instructions 323A that may bestored in non-transitory memory 322A and executable by the at least oneprocessor 321A. The base station 2, 120B, may comprise at least onecommunication interface 320B, at least one processor 321B, and at leastone set of program code instructions 323B that may be stored innon-transitory memory 322B and executable by the at least one processor321B.

A base station may comprise any number of sectors, for example: 1, 2, 3,4, or 6 sectors. A base station may comprise any number of cells, forexample, ranging from 1 to 50 cells or more. A cell may be categorized,for example, as a primary cell or secondary cell. At Radio ResourceControl (RRC) connection establishment, re-establishment, handover,etc., a serving cell may provide NAS (non-access stratum) mobilityinformation (e.g., Tracking Area Identifier (TAI)). At RRC connectionre-establishment and/or handover, a serving cell may provide securityinput. This serving cell may be referred to as the Primary Cell (PCell).In the downlink, a carrier corresponding to the PCell may be a DLPrimary Component Carrier (PCC). In the uplink, a carrier may be an ULPCC. Secondary Cells (SCells) may be configured to form together with aPCell a set of serving cells, for example, depending on wireless devicecapabilities. In a downlink, a carrier corresponding to an SCell may bea downlink secondary component carrier (DL SCC). In an uplink, a carriermay be an uplink secondary component carrier (UL SCC). An SCell may ormay not have an uplink carrier.

A cell, comprising a downlink carrier and optionally an uplink carrier,may be assigned a physical cell ID and/or a cell index. A carrier(downlink and/or uplink) may belong to one cell. The cell ID and/or cellindex may identify the downlink carrier and/or uplink carrier of thecell (e.g., depending on the context it is used). A cell ID may beequally referred to as a carrier ID, and a cell index may be referred toas a carrier index. A physical cell ID and/or a cell index may beassigned to a cell. A cell ID may be determined using a synchronizationsignal transmitted via a downlink carrier. A cell index may bedetermined using RRC messages. A first physical cell ID for a firstdownlink carrier may indicate that the first physical cell ID is for acell comprising the first downlink carrier. The same concept may beused, for example, with carrier activation and/or deactivation (e.g.,secondary cell activation and/or deactivation). A first carrier that isactivated may indicate that a cell comprising the first carrier isactivated.

A base station may send (e.g., transmit) to a wireless device one ormore messages (e.g., RRC messages) comprising a plurality ofconfiguration parameters for one or more cells. One or more cells maycomprise at least one primary cell and at least one secondary cell. AnRRC message may be broadcasted and/or unicasted to the wireless device.Configuration parameters may comprise common parameters and dedicatedparameters.

Services and/or functions of an RRC sublayer may comprise at least oneof: broadcast of system information related to AS and/or NAS; paginginitiated by a 5GC and/or an NG-RAN; establishment, maintenance, and/orrelease of an RRC connection between a wireless device and an NG-RAN,which may comprise at least one of addition, modification, and/orrelease of carrier aggregation; and/or addition, modification, and/orrelease of dual connectivity in NR or between E-UTRA and NR. Servicesand/or functions of an RRC sublayer may comprise at least one ofsecurity functions comprising key management; establishment,configuration, maintenance, and/or release of Signaling Radio Bearers(SRBs) and/or Data Radio Bearers (DRBs); mobility functions which maycomprise at least one of a handover (e.g., intra NR mobility orinter-RAT mobility) and/or a context transfer; and/or a wireless devicecell selection and/or reselection and/or control of cell selection andreselection. Services and/or functions of an RRC sublayer may compriseat least one of QoS management functions; a wireless device measurementconfiguration/reporting; detection of and/or recovery from radio linkfailure; and/or NAS message transfer to and/or from a core networkentity (e.g., AMF, Mobility Management Entity (MME)) from and/or to thewireless device.

An RRC sublayer may support an RRC_Idle state, an RRC_Inactive state,and/or an RRC_Connected state for a wireless device. In an RRC_Idlestate, a wireless device may perform at least one of: Public Land MobileNetwork (PLMN) selection; receiving broadcasted system information; cellselection and/or re-selection; monitoring and/or receiving a paging formobile terminated data initiated by 5GC; paging for mobile terminateddata area managed by 5GC; and/or DRX for CN paging configured via NAS.In an RRC_Inactive state, a wireless device may perform at least one of:receiving broadcasted system information; cell selection and/orre-selection; monitoring and/or receiving a RAN and/or CN paginginitiated by an NG-RAN and/or a 5GC; RAN-based notification area (RNA)managed by an NG-RAN; and/or DRX for a RAN and/or CN paging configuredby NG-RAN/NAS. In an RRC_Idle state of a wireless device, a base station(e.g., NG-RAN) may keep a 5GC-NG-RAN connection (e.g., both C/U-planes)for the wireless device; and/or store a wireless device AS context forthe wireless device. In an RRC_Connected state of a wireless device, abase station (e.g., NG-RAN) may perform at least one of: establishmentof 5GC-NG-RAN connection (both C/U-planes) for the wireless device;storing a UE AS context for the wireless device; send (e.g., transmit)and/or receive of unicast data to and/or from the wireless device;and/or network-controlled mobility based on measurement results receivedfrom the wireless device. In an RRC_Connected state of a wirelessdevice, an NG-RAN may know a cell to which the wireless device belongs.

System information (SI) may be divided into minimum SI and other SI. Theminimum SI may be periodically broadcast. The minimum SI may comprisebasic information required for initial access and/or information foracquiring any other SI broadcast periodically and/or provisionedon-demand (e.g., scheduling information). The other SI may either bebroadcast, and/or be provisioned in a dedicated manner, such as eithertriggered by a network and/or upon request from a wireless device. Aminimum SI may be transmitted via two different downlink channels usingdifferent messages (e.g., MasterinformationBlock andSystemInformationBlockType1). Another SI may be transmitted viaSystemInformationBlockType2. For a wireless device in an RRC_Connectedstate, dedicated RRC signalling may be used for the request and deliveryof the other SI. For the wireless device in the RRC_Idle state and/or inthe RRC_Inactive state, the request may trigger a random accessprocedure.

A wireless device may report its radio access capability information,which may be static. A base station may request one or more indicationsof capabilities for a wireless device to report based on bandinformation. A temporary capability restriction request may be sent bythe wireless device (e.g., if allowed by a network) to signal thelimited availability of some capabilities (e.g., due to hardwaresharing, interference, and/or overheating) to the base station. The basestation may confirm or reject the request. The temporary capabilityrestriction may be transparent to 5GC (e.g., static capabilities may bestored in 5GC).

A wireless device may have an RRC connection with a network, forexample, if CA is configured. At RRC connection establishment,re-establishment, and/or handover procedures, a serving cell may provideNAS mobility information. At RRC connection re-establishment and/orhandover, a serving cell may provide a security input. This serving cellmay be referred to as the PCell. SCells may be configured to formtogether with the PCell a set of serving cells, for example, dependingon the capabilities of the wireless device. The configured set ofserving cells for the wireless device may comprise a PCell and one ormore SCells.

The reconfiguration, addition, and/or removal of SCells may be performedby RRC messaging. At intra-NR handover, RRC may add, remove, and/orreconfigure SCells for usage with the target PCell. Dedicated RRCsignaling may be used (e.g., if adding a new SCell) to send all requiredsystem information of the SCell (e.g., if in connected mode, wirelessdevices may not acquire broadcasted system information directly from theSCells).

The purpose of an RRC connection reconfiguration procedure may be tomodify an RRC connection, (e.g., to establish, modify, and/or releaseRBs; to perform handover; to setup, modify, and/or release measurements,for example, to add, modify, and/or release SCells and cell groups). NASdedicated information may be transferred from the network to thewireless device, for example, as part of the RRC connectionreconfiguration procedure. The RRCConnectionReconfiguration message maybe a command to modify an RRC connection. One or more RRC messages mayconvey information for measurement configuration, mobility control,and/or radio resource configuration (e.g., RBs, MAC main configuration,and/or physical channel configuration), which may comprise anyassociated dedicated NAS information and/or security configuration. Thewireless device may perform an SCell release, for example, if thereceived RRC Connection Reconfiguration message includes thesCellToReleaseList. The wireless device may perform SCell additions ormodification, for example, if the received RRC ConnectionReconfiguration message includes the sCellToAddModList.

An RRC connection establishment, reestablishment, and/or resumeprocedure may be to establish, reestablish, and/or resume an RRCconnection, respectively. An RRC connection establishment procedure maycomprise SRB1 establishment. The RRC connection establishment proceduremay be used to transfer the initial NAS dedicated information and/ormessage from a wireless device to an E-UTRAN. TheRRCConnectionReestablishment message may be used to re-establish SRB1.

A measurement report procedure may be used to transfer measurementresults from a wireless device to an NG-RAN. The wireless device mayinitiate a measurement report procedure, for example, after successfulsecurity activation. A measurement report message may be used to send(e.g., transmit) measurement results.

The wireless device 110 may comprise at least one communicationinterface 310 (e.g., a wireless modem, an antenna, and/or the like), atleast one processor 314, and at least one set of program codeinstructions 316 that may be stored in non-transitory memory 315 andexecutable by the at least one processor 314. The wireless device 110may further comprise at least one of at least one speaker and/ormicrophone 311, at least one keypad 312, at least one display and/ortouchpad 313, at least one power source 317, at least one globalpositioning system (GPS) chipset 318, and/or other peripherals 319.

The processor 314 of the wireless device 110, the processor 321A of thebase station 1 120A, and/or the processor 321B of the base station 2120B may comprise at least one of a general-purpose processor, a digitalsignal processor (DSP), a controller, a microcontroller, an applicationspecific integrated circuit (ASIC), a field programmable gate array(FPGA) and/or other programmable logic device, discrete gate and/ortransistor logic, discrete hardware components, and/or the like. Theprocessor 314 of the wireless device 110, the processor 321A in basestation 1 120A, and/or the processor 321B in base station 2 120B mayperform at least one of signal coding and/or processing, dataprocessing, power control, input/output processing, and/or any otherfunctionality that may enable the wireless device 110, the base station1 120A and/or the base station 2 120B to operate in a wirelessenvironment.

The processor 314 of the wireless device 110 may be connected to and/orin communication with the speaker and/or microphone 311, the keypad 312,and/or the display and/or touchpad 313. The processor 314 may receiveuser input data from and/or provide user output data to the speakerand/or microphone 311, the keypad 312, and/or the display and/ortouchpad 313. The processor 314 in the wireless device 110 may receivepower from the power source 317 and/or may be configured to distributethe power to the other components in the wireless device 110. The powersource 317 may comprise at least one of one or more dry cell batteries,solar cells, fuel cells, and/or the like. The processor 314 may beconnected to the GPS chipset 318. The GPS chipset 318 may be configuredto provide geographic location information of the wireless device 110.

The processor 314 of the wireless device 110 may further be connected toand/or in communication with other peripherals 319, which may compriseone or more software and/or hardware modules that may provide additionalfeatures and/or functionalities. For example, the peripherals 319 maycomprise at least one of an accelerometer, a satellite transceiver, adigital camera, a universal serial bus (USB) port, a hands-free headset,a frequency modulated (FM) radio unit, a media player, an Internetbrowser, and/or the like.

The communication interface 320A of the base station 1, 120A, and/or thecommunication interface 320B of the base station 2, 120B, may beconfigured to communicate with the communication interface 310 of thewireless device 110, for example, via a wireless link 330A and/or via awireless link 330B, respectively. The communication interface 320A ofthe base station 1, 120A, may communicate with the communicationinterface 320B of the base station 2 and/or other RAN and/or corenetwork nodes.

The wireless link 330A and/or the wireless link 330B may comprise atleast one of a bi-directional link and/or a directional link. Thecommunication interface 310 of the wireless device 110 may be configuredto communicate with the communication interface 320A of the base station1 120A and/or with the communication interface 320B of the base station2 120B. The base station 1 120A and the wireless device 110, and/or thebase station 2 120B and the wireless device 110, may be configured tosend and receive transport blocks, for example, via the wireless link330A and/or via the wireless link 330B, respectively. The wireless link330A and/or the wireless link 330B may use at least one frequencycarrier. Transceiver(s) may be used. A transceiver may be a device thatcomprises both a transmitter and a receiver. Transceivers may be used indevices such as wireless devices, base stations, relay nodes, computingdevices, and/or the like. Radio technology may be implemented in thecommunication interface 310, 320A, and/or 320B, and the wireless link330A and/or 330B. The radio technology may comprise one or more elementsshown in FIG. 4A, FIG. 4B, FIG. 4C, FIG. 4D, FIG. 6 , FIG. 7A, FIG. 7B,FIG. 8 , and associated text, described below.

Other nodes in a wireless network (e.g. AMF, UPF, SMF, etc.) maycomprise one or more communication interfaces, one or more processors,and memory storing instructions. A node (e.g., wireless device, basestation, AMF, SMF, UPF, servers, switches, antennas, and/or the like)may comprise one or more processors, and memory storing instructionsthat when executed by the one or more processors causes the node toperform certain processes and/or functions. Single-carrier and/ormulti-carrier communication operation may be performed. A non-transitorytangible computer readable media may comprise instructions executable byone or more processors to cause operation of single-carrier and/ormulti-carrier communications. An article of manufacture may comprise anon-transitory tangible computer readable machine-accessible mediumhaving instructions encoded thereon for enabling programmable hardwareto cause a node to enable operation of single-carrier and/ormulti-carrier communications. The node may include processors, memory,interfaces, and/or the like.

An interface may comprise at least one of a hardware interface, afirmware interface, a software interface, and/or a combination thereof.The hardware interface may comprise connectors, wires, and/or electronicdevices such as drivers, amplifiers, and/or the like. The softwareinterface may comprise code stored in a memory device to implementprotocol(s), protocol layers, communication drivers, device drivers,combinations thereof, and/or the like. The firmware interface maycomprise a combination of embedded hardware and/or code stored in(and/or in communication with) a memory device to implement connections,electronic device operations, protocol(s), protocol layers,communication drivers, device drivers, hardware operations, combinationsthereof, and/or the like.

A communication network may comprise the wireless device 110, the basestation 1, 120A, the base station 2, 120B, and/or any other device. Thecommunication network may comprise any number and/or type of devices,such as, for example, computing devices, wireless devices, mobiledevices, handsets, tablets, laptops, internet of things (IoT) devices,hotspots, cellular repeaters, computing devices, and/or, more generally,user equipment (e.g., UE). Although one or more of the above types ofdevices may be referenced herein (e.g., UE, wireless device, computingdevice, etc.), it should be understood that any device herein maycomprise any one or more of the above types of devices or similardevices. The communication network, and any other network referencedherein, may comprise an LTE network, a 5G network, or any other networkfor wireless communications. Apparatuses, systems, and/or methodsdescribed herein may generally be described as implemented on one ormore devices (e.g., wireless device, base station, eNB, gNB, computingdevice, etc.), in one or more networks, but it will be understood thatone or more features and steps may be implemented on any device and/orin any network. As used throughout, the term “base station” may compriseone or more of: a base station, a node, a Node B, a gNB, an eNB, anng-eNB, a relay node (e.g., an integrated access and backhaul (IAB)node), a donor node (e.g., a donor eNB, a donor gNB, etc.), an accesspoint (e.g., a WiFi access point), a computing device, a device capableof wirelessly communicating, or any other device capable of sendingand/or receiving signals. As used throughout, the term “wireless device”may comprise one or more of: a UE, a handset, a mobile device, acomputing device, a node, a device capable of wirelessly communicating,or any other device capable of sending and/or receiving signals. Anyreference to one or more of these terms/devices also considers use ofany other term/device mentioned above.

FIG. 4A, FIG. 4B, FIG. 4C and FIG. 4D show examples of uplink anddownlink signal transmission. FIG. 4A shows an example uplinktransmitter for at least one physical channel A baseband signalrepresenting a physical uplink shared channel may perform one or morefunctions. The one or more functions may comprise at least one of:scrambling (e.g., by Scrambling); modulation of scrambled bits togenerate complex-valued symbols (e.g., by a Modulation mapper); mappingof the complex-valued modulation symbols onto one or severaltransmission layers (e.g., by a Layer mapper); transform precoding togenerate complex-valued symbols (e.g., by a Transform precoder);precoding of the complex-valued symbols (e.g., by a Precoder); mappingof precoded complex-valued symbols to resource elements (e.g., by aResource element mapper); generation of complex-valued time-domainSingle Carrier-Frequency Division Multiple Access (SC-FDMA) or CP-OFDMsignal for an antenna port (e.g., by a signal gen.); and/or the like. ASC-FDMA signal for uplink transmission may be generated, for example, iftransform precoding is enabled. A CP-OFDM signal for uplink transmissionmay be generated by FIG. 4A, for example, if transform precoding is notenabled. These functions are shown as examples and other mechanisms maybe implemented.

FIG. 4B shows an example of modulation and up-conversion to the carrierfrequency of a complex-valued SC-FDMA or CP-OFDM baseband signal for anantenna port and/or for the complex-valued Physical Random AccessCHannel (PRACH) baseband signal. Filtering may be performed prior totransmission.

FIG. 4C shows an example of downlink transmissions. The baseband signalrepresenting a downlink physical channel may perform one or morefunctions. The one or more functions may comprise: scrambling of codedbits in a codeword to be transmitted on a physical channel (e.g., byScrambling); modulation of scrambled bits to generate complex-valuedmodulation symbols (e.g., by a Modulation mapper); mapping of thecomplex-valued modulation symbols onto one or several transmissionlayers (e.g., by a Layer mapper); precoding of the complex-valuedmodulation symbols on a layer for transmission on the antenna ports(e.g., by Precoding); mapping of complex-valued modulation symbols foran antenna port to resource elements (e.g., by a Resource elementmapper); generation of complex-valued time-domain OFDM signal for anantenna port (e.g., by an OFDM signal gen.); and/or the like. Thesefunctions are shown as examples and other mechanisms may be implemented.

A base station may send (e.g., transmit) a first symbol and a secondsymbol on an antenna port, to a wireless device. The wireless device mayinfer the channel (e.g., fading gain, multipath delay, etc.) forconveying the second symbol on the antenna port, from the channel forconveying the first symbol on the antenna port. A first antenna port anda second antenna port may be quasi co-located, for example, if one ormore large-scale properties of the channel over which a first symbol onthe first antenna port is conveyed may be inferred from the channel overwhich a second symbol on a second antenna port is conveyed. The one ormore large-scale properties may comprise at least one of: delay spread;Doppler spread; Doppler shift; average gain; average delay; and/orspatial receiving (Rx) parameters.

FIG. 4D shows an example modulation and up-conversion to the carrierfrequency of the complex-valued OFDM baseband signal for an antennaport. Filtering may be performed prior to transmission.

FIG. 5A shows example uplink channel mapping and example uplink physicalsignals. A physical layer may provide one or more information transferservices to a MAC and/or one or more higher layers. The physical layermay provide the one or more information transfer services to the MAC viaone or more transport channels. An information transfer service mayindicate how and/or with what characteristics data is transferred overthe radio interface.

Uplink transport channels may comprise an Uplink-Shared CHannel (UL-SCH)501 and/or a Random Access CHannel (RACH) 502. A wireless device maysend (e.g., transmit) one or more uplink DM-RSs 506 to a base stationfor channel estimation, for example, for coherent demodulation of one ormore uplink physical channels (e.g., PUSCH 503 and/or PUCCH 504). Thewireless device may send (e.g., transmit) to a base station at least oneuplink DM-RS 506 with PUSCH 503 and/or PUCCH 504, wherein the at leastone uplink DM-RS 506 may be spanning a same frequency range as acorresponding physical channel. The base station may configure thewireless device with one or more uplink DM-RS configurations. At leastone DM-RS configuration may support a front-loaded DM-RS pattern. Afront-loaded DM-RS may be mapped over one or more OFDM symbols (e.g., 1or 2 adjacent OFDM symbols). One or more additional uplink DM-RS may beconfigured to send (e.g., transmit) at one or more symbols of a PUSCHand/or PUCCH. The base station may semi-statically configure thewireless device with a maximum number of front-loaded DM-RS symbols forPUSCH and/or PUCCH. The wireless device may schedule a single-symbolDM-RS and/or double symbol DM-RS based on a maximum number offront-loaded DM-RS symbols, wherein the base station may configure thewireless device with one or more additional uplink DM-RS for PUSCHand/or PUCCH. A new radio network may support, for example, at least forCP-OFDM, a common DM-RS structure for DL and UL, wherein a DM-RSlocation, DM-RS pattern, and/or scrambling sequence may be same ordifferent.

Whether or not an uplink PT-RS 507 is present may depend on an RRCconfiguration. A presence of the uplink PT-RS may be wirelessdevice-specifically configured. A presence and/or a pattern of theuplink PT-RS 507 in a scheduled resource may be wirelessdevice-specifically configured by a combination of RRC signaling and/orassociation with one or more parameters used for other purposes (e.g.,Modulation and Coding Scheme (MCS)) which may be indicated by DCI. Ifconfigured, a dynamic presence of uplink PT-RS 507 may be associatedwith one or more DCI parameters comprising at least a MCS. A radionetwork may support a plurality of uplink PT-RS densities defined intime/frequency domain. If present, a frequency domain density may beassociated with at least one configuration of a scheduled bandwidth. Awireless device may assume a same precoding for a DMRS port and a PT-RSport. A number of PT-RS ports may be less than a number of DM-RS portsin a scheduled resource. The uplink PT-RS 507 may be confined in thescheduled time/frequency duration for a wireless device.

A wireless device may send (e.g., transmit) an SRS 508 to a base stationfor channel state estimation, for example, to support uplink channeldependent scheduling and/or link adaptation. The SRS 508 sent (e.g.,transmitted) by the wireless device may allow for the base station toestimate an uplink channel state at one or more different frequencies. Abase station scheduler may use an uplink channel state to assign one ormore resource blocks of a certain quality (e.g., above a qualitythreshold) for an uplink PUSCH transmission from the wireless device.The base station may semi-statically configure the wireless device withone or more SRS resource sets. For an SRS resource set, the base stationmay configure the wireless device with one or more SRS resources. An SRSresource set applicability may be configured by a higher layer (e.g.,RRC) parameter. An SRS resource in each of one or more SRS resource setsmay be sent (e.g., transmitted) at a time instant, for example, if ahigher layer parameter indicates beam management. The wireless devicemay send (e.g., transmit) one or more SRS resources in different SRSresource sets simultaneously. A new radio network may support aperiodic,periodic, and/or semi-persistent SRS transmissions. The wireless devicemay send (e.g., transmit) SRS resources, for example, based on one ormore trigger types. The one or more trigger types may comprise higherlayer signaling (e.g., RRC) and/or one or more DCI formats (e.g., atleast one DCI format may be used for a wireless device to select atleast one of one or more configured SRS resource sets). An SRS triggertype 0 may refer to an SRS triggered based on a higher layer signaling.An SRS trigger type 1 may refer to an SRS triggered based on one or moreDCI formats. The wireless device may be configured to send (e.g.,transmit) the SRS 508 after a transmission of PUSCH 503 andcorresponding uplink DM-RS 506, for example, if PUSCH 503 and the SRS508 are transmitted in a same slot.

A base station may semi-statically configure a wireless device with oneor more SRS configuration parameters indicating at least one offollowing: an SRS resource configuration identifier, a number of SRSports, time domain behavior of SRS resource configuration (e.g., anindication of periodic, semi-persistent, or aperiodic SRS), slot(mini-slot, and/or subframe) level periodicity and/or offset for aperiodic and/or aperiodic SRS resource, a number of OFDM symbols in aSRS resource, starting OFDM symbol of a SRS resource, an SRS bandwidth,a frequency hopping bandwidth, a cyclic shift, and/or an SRS sequenceID.

FIG. 5B shows an example downlink channel mapping and downlink physicalsignals. Downlink transport channels may comprise a Downlink-SharedCHannel (DL-SCH) 511, a Paging CHannel (PCH) 512, and/or a BroadcastCHannel (BCH) 513. A transport channel may be mapped to one or morecorresponding physical channels. A UL-SCH 501 may be mapped to aPhysical Uplink Shared CHannel (PUSCH) 503. A RACH 502 may be mapped toa PRACH 505. A DL-SCH 511 and a PCH 512 may be mapped to a PhysicalDownlink Shared CHannel (PDSCH) 514. A BCH 513 may be mapped to aPhysical Broadcast CHannel (PBCH) 516.

A radio network may comprise one or more downlink and/or uplinktransport channels. The radio network may comprise one or more physicalchannels without a corresponding transport channel. The one or morephysical channels may be used for an Uplink Control Information (UCI)509 and/or a Downlink Control Information (DCI) 517. A Physical UplinkControl CHannel (PUCCH) 504 may carry UCI 509 from a wireless device toa base station. A Physical Downlink Control CHannel (PDCCH) 515 maycarry the DCI 517 from a base station to a wireless device. The radionetwork (e.g., NR) may support the UCI 509 multiplexing in the PUSCH503, for example, if the UCI 509 and the PUSCH 503 transmissions maycoincide in a slot (e.g., at least in part). The UCI 509 may comprise atleast one of a CSI, an Acknowledgement (ACK)/Negative Acknowledgement(NACK), and/or a scheduling request. The DCI 517 via the PDCCH 515 mayindicate at least one of following: one or more downlink assignmentsand/or one or more uplink scheduling grants.

In uplink, a wireless device may send (e.g., transmit) one or moreReference Signals (RSs) to a base station. The one or more RSs maycomprise at least one of a Demodulation-RS (DM-RS) 506, a PhaseTracking-RS (PT-RS) 507, and/or a Sounding RS (SRS) 508. In downlink, abase station may send (e.g., transmit, unicast, multicast, and/orbroadcast) one or more RSs to a wireless device. The one or more RSs maycomprise at least one of a Primary Synchronization Signal(PSS)/Secondary Synchronization Signal (SSS) 521, a CSI-RS 522, a DM-RS523, and/or a PT-RS 524.

In a time domain, an SS/PBCH block may comprise one or more OFDM symbols(e.g., 4 OFDM symbols numbered in increasing order from 0 to 3) withinthe SS/PBCH block. An SS/PBCH block may comprise the PSS/SSS 521 and/orthe PBCH 516. In the frequency domain, an SS/PBCH block may comprise oneor more contiguous subcarriers (e.g., 240 contiguous subcarriers withthe subcarriers numbered in increasing order from 0 to 239) within theSS/PBCH block. The PSS/SSS 521 may occupy, for example, 1 OFDM symboland 127 subcarriers. The PBCH 516 may span across, for example, 3 OFDMsymbols and 240 subcarriers. A wireless device may assume that one ormore SS/PBCH blocks transmitted with a same block index may be quasico-located, for example, with respect to Doppler spread, Doppler shift,average gain, average delay, and/or spatial Rx parameters. A wirelessdevice may not assume quasi co-location for other SS/PBCH blocktransmissions. A periodicity of an SS/PBCH block may be configured by aradio network (e.g., by an RRC signaling). One or more time locations inwhich the SS/PBCH block may be sent may be determined by sub-carrierspacing. A wireless device may assume a band-specific sub-carrierspacing for an SS/PBCH block, for example, unless a radio network hasconfigured the wireless device to assume a different sub-carrierspacing.

The downlink CSI-RS 522 may be used for a wireless device to acquirechannel state information. A radio network may support periodic,aperiodic, and/or semi-persistent transmission of the downlink CSI-RS522. A base station may semi-statically configure and/or reconfigure awireless device with periodic transmission of the downlink CSI-RS 522. Aconfigured CSI-RS resources may be activated and/or deactivated. Forsemi-persistent transmission, an activation and/or deactivation of aCSI-RS resource may be triggered dynamically. A CSI-RS configuration maycomprise one or more parameters indicating at least a number of antennaports. A base station may configure a wireless device with 32 ports, orany other number of ports. A base station may semi-statically configurea wireless device with one or more CSI-RS resource sets. One or moreCSI-RS resources may be allocated from one or more CSI-RS resource setsto one or more wireless devices. A base station may semi-staticallyconfigure one or more parameters indicating CSI RS resource mapping, forexample, time-domain location of one or more CSI-RS resources, abandwidth of a CSI-RS resource, and/or a periodicity. A wireless devicemay be configured to use the same OFDM symbols for the downlink CSI-RS522 and the Control Resource Set (CORESET), for example, if the downlinkCSI-RS 522 and the CORESET are spatially quasi co-located and resourceelements associated with the downlink CSI-RS 522 are the outside of PRBsconfigured for the CORESET. A wireless device may be configured to usethe same OFDM symbols for downlink CSI-RS 522 and SS/PBCH blocks, forexample, if the downlink CSI-RS 522 and SS/PBCH blocks are spatiallyquasi co-located and resource elements associated with the downlinkCSI-RS 522 are outside of the PRBs configured for the SS/PBCH blocks.

A wireless device may send (e.g., transmit) one or more downlink DM-RSs523 to a base station for channel estimation, for example, for coherentdemodulation of one or more downlink physical channels (e.g., PDSCH514). A radio network may support one or more variable and/orconfigurable DM-RS patterns for data demodulation. At least one downlinkDM-RS configuration may support a front-loaded DM-RS pattern. Afront-loaded DM-RS may be mapped over one or more OFDM symbols (e.g., 1or 2 adjacent OFDM symbols). A base station may semi-staticallyconfigure a wireless device with a maximum number of front-loaded DM-RSsymbols for PDSCH 514. A DM-RS configuration may support one or moreDM-RS ports. A DM-RS configuration may support at least 8 orthogonaldownlink DM-RS ports, for example, for single user-MIMO. ADM-RSconfiguration may support 12 orthogonal downlink DM-RS ports, forexample, for multiuser-MIMO. A radio network may support, for example,at least for CP-OFDM, a common DM-RS structure for DL and UL, wherein aDM-RS location, DM-RS pattern, and/or scrambling sequence may be thesame or different.

Whether or not the downlink PT-RS 524 is present may depend on an RRCconfiguration. A presence of the downlink PT-RS 524 may be wirelessdevice-specifically configured. A presence and/or a pattern of thedownlink PT-RS 524 in a scheduled resource may be wirelessdevice-specifically configured, for example, by a combination of RRCsignaling and/or an association with one or more parameters used forother purposes (e.g., MCS) which may be indicated by the DCI. Ifconfigured, a dynamic presence of the downlink PT-RS 524 may beassociated with one or more DCI parameters comprising at least MCS. Aradio network may support a plurality of PT-RS densities in atime/frequency domain. If present, a frequency domain density may beassociated with at least one configuration of a scheduled bandwidth. Awireless device may assume the same precoding for a DMRS port and aPT-RS port. A number of PT-RS ports may be less than a number of DM-RSports in a scheduled resource. The downlink PT-RS 524 may be confined inthe scheduled time/frequency duration for a wireless device.

FIG. 6 shows an example transmission time and reception time for acarrier. A multicarrier OFDM communication system may include one ormore carriers, for example, ranging from 1 to 32 carriers (such as forcarrier aggregation) or ranging from 1 to 64 carriers (such as for dualconnectivity). Different radio frame structures may be supported (e.g.,for FDD and/or for TDD duplex mechanisms). FIG. 6 shows an example frametiming. Downlink and uplink transmissions may be organized into radioframes 601. Radio frame duration may be 10 milliseconds (ms). A 10 msradio frame 601 may be divided into ten equally sized subframes 602,each with a 1 ms duration. Subframe(s) may comprise one or more slots(e.g., slots 603 and 605) depending on subcarrier spacing and/or CPlength. For example, a subframe with 15 kHz, 30 kHz, 60 kHz, 120 kHz,240 kHz and 480 kHz subcarrier spacing may comprise one, two, four,eight, sixteen and thirty-two slots, respectively. In FIG. 6 , asubframe may be divided into two equally sized slots 603 with 0.5 msduration. For example, 10 subframes may be available for downlinktransmission and 10 subframes may be available for uplink transmissionsin a 10 ms interval. Other subframe durations such as, for example, 0.5ms, 1 ms, 2 ms, and 5 ms may be supported. Uplink and downlinktransmissions may be separated in the frequency domain. Slot(s) mayinclude a plurality of OFDM symbols 604. The number of OFDM symbols 604in a slot 605 may depend on the cyclic prefix length. A slot may be 14OFDM symbols for the same subcarrier spacing of up to 480 kHz withnormal CP. A slot may be 12 OFDM symbols for the same subcarrier spacingof 60 kHz with extended CP. A slot may comprise downlink, uplink, and/ora downlink part and an uplink part, and/or alike.

FIG. 7A shows example sets of OFDM subcarriers. A base station maycommunicate with a wireless device using a carrier having an examplechannel bandwidth 700. Arrow(s) in the example may depict a subcarrierin a multicarrier OFDM system. The OFDM system may use technology suchas OFDM technology, SC-FDMA technology, and/or the like. An arrow 701shows a subcarrier transmitting information symbols. A subcarrierspacing 702, between two contiguous subcarriers in a carrier, may be anyone of 15 kHz, 30 kHz, 60 kHz, 120 kHz, 240 kHz, or any other frequency.Different subcarrier spacing may correspond to different transmissionnumerologies. A transmission numerology may comprise at least: anumerology index; a value of subcarrier spacing; and/or a type of cyclicprefix (CP). A base station may send (e.g., transmit) to and/or receivefrom a wireless device via a number of subcarriers 703 in a carrier. Abandwidth occupied by a number of subcarriers 703 (e.g., transmissionbandwidth) may be smaller than the channel bandwidth 700 of a carrier,for example, due to guard bands 704 and 705. Guard bands 704 and 705 maybe used to reduce interference to and from one or more neighborcarriers. A number of subcarriers (e.g., transmission bandwidth) in acarrier may depend on the channel bandwidth of the carrier and/or thesubcarrier spacing. A transmission bandwidth, for a carrier with a 20MHz channel bandwidth and a 15 kHz subcarrier spacing, may be in numberof 1024 subcarriers.

A base station and a wireless device may communicate with multiplecomponent carriers (CCs), for example, if configured with CA. Differentcomponent carriers may have different bandwidth and/or differentsubcarrier spacing, for example, if CA is supported. A base station maysend (e.g., transmit) a first type of service to a wireless device via afirst component carrier. The base station may send (e.g., transmit) asecond type of service to the wireless device via a second componentcarrier. Different types of services may have different servicerequirements (e.g., data rate, latency, reliability), which may besuitable for transmission via different component carriers havingdifferent subcarrier spacing and/or different bandwidth.

FIG. 7B shows examples of component carriers. A first component carriermay comprise a first number of subcarriers 706 having a first subcarrierspacing 709. A second component carrier may comprise a second number ofsubcarriers 707 having a second subcarrier spacing 710. A thirdcomponent carrier may comprise a third number of subcarriers 708 havinga third subcarrier spacing 711. Carriers in a multicarrier OFDMcommunication system may be contiguous carriers, non-contiguouscarriers, or a combination of both contiguous and non-contiguouscarriers.

FIG. 8 shows an example of OFDM radio resources. A carrier may have atransmission bandwidth 801. A resource grid may be in a structure offrequency domain 802 and time domain 803. A resource grid may comprise afirst number of OFDM symbols in a subframe and a second number ofresource blocks, starting from a common resource block indicated byhigher-layer signaling (e.g., RRC signaling), for a transmissionnumerology and a carrier. In a resource grid, a resource element 805 maycomprise a resource unit that may be identified by a subcarrier indexand a symbol index. A subframe may comprise a first number of OFDMsymbols 807 that may depend on a numerology associated with a carrier. Asubframe may have 14 OFDM symbols for a carrier, for example, if asubcarrier spacing of a numerology of a carrier is 15 kHz. A subframemay have 28 OFDM symbols, for example, if a subcarrier spacing of anumerology is 30 kHz. A subframe may have 56 OFDM symbols, for example,if a subcarrier spacing of a numerology is 60 kHz. A subcarrier spacingof a numerology may comprise any other frequency. A second number ofresource blocks comprised in a resource grid of a carrier may depend ona bandwidth and a numerology of the carrier.

A resource block 806 may comprise 12 subcarriers. Multiple resourceblocks may be grouped into a Resource Block Group (RBG) 804. A size of aRBG may depend on at least one of: a RRC message indicating a RBG sizeconfiguration; a size of a carrier bandwidth; and/or a size of abandwidth part of a carrier. A carrier may comprise multiple bandwidthparts. A first bandwidth part of a carrier may have a differentfrequency location and/or a different bandwidth from a second bandwidthpart of the carrier.

A base station may send (e.g., transmit), to a wireless device, adownlink control information comprising a downlink or uplink resourceblock assignment. A base station may send (e.g., transmit) to and/orreceive from, a wireless device, data packets (e.g., transport blocks).The data packets may be scheduled on and transmitted via one or moreresource blocks and one or more slots indicated by parameters indownlink control information and/or RRC message(s). A starting symbolrelative to a first slot of the one or more slots may be indicated tothe wireless device. A base station may send (e.g., transmit) to and/orreceive from, a wireless device, data packets. The data packets may bescheduled for transmission on one or more RBGs and in one or more slots.

A base station may send (e.g., transmit), to a wireless device, downlinkcontrol information comprising a downlink assignment. The base stationmay send (e.g., transmit) the DCI via one or more PDCCHs. The downlinkassignment may comprise parameters indicating at least one of amodulation and coding format; resource allocation; and/or HARQinformation related to the DL-SCH. The resource allocation may compriseparameters of resource block allocation; and/or slot allocation. A basestation may allocate (e.g., dynamically) resources to a wireless device,for example, via a Cell-Radio Network Temporary Identifier (C-RNTI) onone or more PDCCHs. The wireless device may monitor the one or morePDCCHs, for example, in order to find possible allocation if itsdownlink reception is enabled. The wireless device may receive one ormore downlink data packets on one or more PDSCH scheduled by the one ormore PDCCHs, for example, if the wireless device successfully detectsthe one or more PDCCHs.

A base station may allocate Configured Scheduling (CS) resources fordown link transmission to a wireless device. The base station may send(e.g., transmit) one or more RRC messages indicating a periodicity ofthe CS grant. The base station may send (e.g., transmit) DCI via a PDCCHaddressed to a Configured Scheduling-RNTI (CS-RNTI) activating the CSresources. The DCI may comprise parameters indicating that the downlinkgrant is a CS grant. The CS grant may be implicitly reused according tothe periodicity defined by the one or more RRC messages. The CS grantmay be implicitly reused, for example, until deactivated.

A base station may send (e.g., transmit), to a wireless device via oneor more PDCCHs, downlink control information comprising an uplink grant.The uplink grant may comprise parameters indicating at least one of amodulation and coding format; a resource allocation; and/or HARQinformation related to the UL-SCH. The resource allocation may compriseparameters of resource block allocation; and/or slot allocation. Thebase station may dynamically allocate resources to the wireless devicevia a C-RNTI on one or more PDCCHs. The wireless device may monitor theone or more PDCCHs, for example, in order to find possible resourceallocation. The wireless device may send (e.g., transmit) one or moreuplink data packets via one or more PUSCH scheduled by the one or morePDCCHs, for example, if the wireless device successfully detects the oneor more PDCCHs.

The base station may allocate CS resources for uplink data transmissionto a wireless device. The base station may transmit one or more RRCmessages indicating a periodicity of the CS grant. The base station maysend (e.g., transmit) DCI via a PDCCH addressed to a CS-RNTI to activatethe CS resources. The DCI may comprise parameters indicating that theuplink grant is a CS grant. The CS grant may be implicitly reusedaccording to the periodicity defined by the one or more RRC message, TheCS grant may be implicitly reused, for example, until deactivated.

A base station may send (e.g., transmit) DCI and/or control signalingvia a PDCCH. The DCI may comprise a format of a plurality of formats.The DCI may comprise downlink and/or uplink scheduling information(e.g., resource allocation information, HARQ related parameters, MCS),request(s) for CSI (e.g., aperiodic CQI reports), request(s) for an SRS,uplink power control commands for one or more cells, one or more timinginformation (e.g., TB transmission/reception timing, HARQ feedbacktiming, etc.), and/or the like. The DCI may indicate an uplink grantcomprising transmission parameters for one or more transport blocks. TheDCI may indicate a downlink assignment indicating parameters forreceiving one or more transport blocks. The DCI may be used by the basestation to initiate a contention-free random access at the wirelessdevice. The base station may send (e.g., transmit) DCI comprising a slotformat indicator (SFI) indicating a slot format. The base station maysend (e.g., transmit) DCI comprising a preemption indication indicatingthe PRB(s) and/or OFDM symbol(s) in which a wireless device may assumeno transmission is intended for the wireless device. The base stationmay send (e.g., transmit) DCI for group power control of the PUCCH, thePUSCH, and/or an SRS. DCI may correspond to an RNTI. The wireless devicemay obtain an RNTI after or in response to completing the initial access(e.g., C-RNTI). The base station may configure an RNTI for the wireless(e.g., CS-RNTI, TPC-CS-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI,TPC-SRS-RNTI, etc.). The wireless device may determine (e.g., compute)an RNTI (e.g., the wireless device may determine the RA-RNTI based onresources used for transmission of a preamble). An RNTI may have apre-configured value (e.g., P-RNTI or SI-RNTI). The wireless device maymonitor a group common search space which may be used by the basestation for sending (e.g., transmitting) DCIs that are intended for agroup of wireless devices. A group common DCI may correspond to an RNTIwhich is commonly configured for a group of wireless devices. Thewireless device may monitor a wireless device-specific search space. Awireless device specific DCI may correspond to an RNTI configured forthe wireless device.

A communications system (e.g., an NR system) may support a single beamoperation and/or a multi-beam operation. In a multi-beam operation, abase station may perform a downlink beam sweeping to provide coveragefor common control channels and/or downlink SS blocks, which maycomprise at least a PSS, a SSS, and/or PBCH. A wireless device maymeasure quality of a beam pair link using one or more RSs. One or moreSS blocks, or one or more CSI-RS resources (e.g., which may beassociated with a CSI-RS resource index (CRI)), and/or one or moreDM-RSs of a PBCH, may be used as an RS for measuring a quality of a beampair link. The quality of a beam pair link may be based on a referencesignal received power (RSRP) value, a reference signal received quality(RSRQ) value, and/or a CSI value measured on RS resources. The basestation may indicate whether an RS resource, used for measuring a beampair link quality, is quasi-co-located (QCLed) with DM-RSs of a controlchannel. An RS resource and DM-RSs of a control channel may be calledQCLed, for example, if channel characteristics from a transmission on anRS to a wireless device, and that from a transmission on a controlchannel to a wireless device, are similar or the same under a configuredcriterion. In a multi-beam operation, a wireless device may perform anuplink beam sweeping to access a cell.

A wireless device may be configured to monitor a PDCCH on one or morebeam pair links simultaneously, for example, depending on a capabilityof the wireless device. This monitoring may increase robustness againstbeam pair link blocking. A base station may send (e.g., transmit) one ormore messages to configure the wireless device to monitor the PDCCH onone or more beam pair links in different PDCCH OFDM symbols. A basestation may send (e.g., transmit) higher layer signaling (e.g., RRCsignaling) and/or a MAC CE comprising parameters related to the Rx beamsetting of the wireless device for monitoring the PDCCH on one or morebeam pair links. The base station may send (e.g., transmit) anindication of a spatial QCL assumption between an DL RS antenna port(s)(e.g., a cell-specific CSI-RS, a wireless device-specific CSI-RS, an SSblock, and/or a PBCH with or without DM-RSs of the PBCH) and/or DL RSantenna port(s) for demodulation of a DL control channel. Signaling forbeam indication for a PDCCH may comprise MAC CE signaling, RRCsignaling, DCI signaling, and/or specification-transparent and/orimplicit method, and/or any combination of signaling methods.

A base station may indicate spatial QCL parameters between DL RS antennaport(s) and DM-RS antenna port(s) of a DL data channel, for example, forreception of a unicast DL data channel. The base station may send (e.g.,transmit) DCI (e.g., downlink grants) comprising information indicatingthe RS antenna port(s). The information may indicate RS antenna port(s)that may be QCL-ed with the DM-RS antenna port(s). A different set ofDM-RS antenna port(s) for a DL data channel may be indicated as QCL witha different set of the RS antenna port(s).

FIG. 9A shows an example of beam sweeping in a DL channel. In anRRC_INACTIVE state or RRC_IDLE state, a wireless device may assume thatSS blocks form an SS burst 940, and an SS burst set 950. The SS burstset 950 may have a given periodicity. A base station 120 may send (e.g.,transmit) SS blocks in multiple beams, together forming a SS burst 940,for example, in a multi-beam operation. One or more SS blocks may besent (e.g., transmitted) on one beam. If multiple SS bursts 940 aretransmitted with multiple beams, SS bursts together may form SS burstset 950.

A wireless device may use CSI-RS for estimating a beam quality of a linkbetween a wireless device and a base station, for example, in the multibeam operation. A beam may be associated with a CSI-RS. A wirelessdevice may (e.g., based on a RSRP measurement on CSI-RS) report a beamindex, which may be indicated in a CRI for downlink beam selectionand/or associated with an RSRP value of a beam. A CSI-RS may be sent(e.g., transmitted) on a CSI-RS resource, which may comprise at leastone of: one or more antenna ports and/or one or more time and/orfrequency radio resources. A CSI-RS resource may be configured in acell-specific way such as by common RRC signaling, or in a wirelessdevice-specific way such as by dedicated RRC signaling and/or L1/L2signaling. Multiple wireless devices covered by a cell may measure acell-specific CSI-RS resource. A dedicated subset of wireless devicescovered by a cell may measure a wireless device-specific CSI-RSresource.

A CSI-RS resource may be sent (e.g., transmitted) periodically, usingaperiodic transmission, or using a multi-shot or semi-persistenttransmission. In a periodic transmission in FIG. 9A, a base station 120may send (e.g., transmit) configured CSI-RS resources 940 periodicallyusing a configured periodicity in a time domain. In an aperiodictransmission, a configured CSI-RS resource may be sent (e.g.,transmitted) in a dedicated time slot. In a multi-shot and/orsemi-persistent transmission, a configured CSI-RS resource may be sent(e.g., transmitted) within a configured period. Beams used for CSI-RStransmission may have a different beam width than beams used forSS-blocks transmission.

FIG. 9B shows an example of a beam management procedure, such as in anexample new radio network. The base station 120 and/or the wirelessdevice 110 may perform a downlink L1/L2 beam management procedure. Oneor more of the following downlink L1/L2 beam management procedures maybe performed within one or more wireless devices 110 and one or morebase stations 120. A P1 procedure 910 may be used to enable the wirelessdevice 110 to measure one or more Transmission (Tx) beams associatedwith the base station 120, for example, to support a selection of afirst set of Tx beams associated with the base station 120 and a firstset of Rx beam(s) associated with the wireless device 110. A basestation 120 may sweep a set of different Tx beams, for example, forbeamforming at a base station 120 (such as shown in the top row, in acounter-clockwise direction). A wireless device 110 may sweep a set ofdifferent Rx beams, for example, for beamforming at a wireless device110 (such as shown in the bottom row, in a clockwise direction). A P2procedure 920 may be used to enable a wireless device 110 to measure oneor more Tx beams associated with a base station 120, for example, topossibly change a first set of Tx beams associated with a base station120. A P2 procedure 920 may be performed on a possibly smaller set ofbeams (e.g., for beam refinement) than in the P1 procedure 910. A P2procedure 920 may be a special example of a P1 procedure 910. A P3procedure 930 may be used to enable a wireless device 110 to measure atleast one Tx beam associated with a base station 120, for example, tochange a first set of Rx beams associated with a wireless device 110.

A wireless device 110 may send (e.g., transmit) one or more beammanagement reports to a base station 120. In one or more beam managementreports, a wireless device 110 may indicate one or more beam pairquality parameters comprising one or more of: a beam identification; anRSRP; a Precoding Matrix Indicator (PMI), Channel Quality Indicator(CQI), and/or Rank Indicator (RI) of a subset of configured beams. Basedon one or more beam management reports, the base station 120 may send(e.g., transmit) to a wireless device 110 a signal indicating that oneor more beam pair links are one or more serving beams. The base station120 may send (e.g., transmit) the PDCCH and the PDSCH for a wirelessdevice 110 using one or more serving beams.

A communications network (e.g., a new radio network) may support aBandwidth Adaptation (BA). Receive and/or transmit bandwidths that maybe configured for a wireless device using a BA may not be large. Receiveand/or transmit bandwidth may not be as large as a bandwidth of a cell.Receive and/or transmit bandwidths may be adjustable. A wireless devicemay change receive and/or transmit bandwidths, for example, to reduce(e.g., shrink) the bandwidth(s) at (e.g., during) a period of lowactivity such as to save power. A wireless device may change a locationof receive and/or transmit bandwidths in a frequency domain, forexample, to increase scheduling flexibility. A wireless device maychange a subcarrier spacing, for example, to allow different services.

A Bandwidth Part (BWP) may comprise a subset of a total cell bandwidthof a cell. A base station may configure a wireless device with one ormore BWPs, for example, to achieve a BA. A base station may indicate, toa wireless device, which of the one or more (configured) BWPs is anactive BWP.

FIG. 10 shows an example of BWP configurations. BWPs may be configuredas follows: BWP1 (1010 and 1050) with a width of 40 MHz and subcarrierspacing of 15 kHz; BWP2 (1020 and 1040) with a width of 10 MHz andsubcarrier spacing of 15 kHz; BWP3 1030 with a width of 20 MHz andsubcarrier spacing of 60 kHz. Any number of BWP configurations maycomprise any other width and subcarrier spacing combination.

A wireless device, configured for operation in one or more BWPs of acell, may be configured by one or more higher layers (e.g., RRC layer).The wireless device may be configured for a cell with: a set of one ormore BWPs (e.g., at most four BWPs) for reception (e.g., a DL BWP set)in a DL bandwidth by at least one parameter DL-BWP; and a set of one ormore BWPs (e.g., at most four BWPs) for transmissions (e.g., UL BWP set)in an UL bandwidth by at least one parameter UL-BWP. BWPs are describedas example resources. Any wireless resource may be applicable to one ormore procedures described herein.

A base station may configure a wireless device with one or more UL andDL BWP pairs, for example, to enable BA on the PCell. To enable BA onSCells (e.g., for CA), a base station may configure a wireless device atleast with one or more DL BWPs (e.g., there may be none in an UL).

An initial active DL BWP may comprise at least one of a location andnumber of contiguous PRBs, a subcarrier spacing, or a cyclic prefix, forexample, for a control resource set for at least one common searchspace. For operation on the PCell, one or more higher layer parametersmay indicate at least one initial UL BWP for a random access procedure.If a wireless device is configured with a secondary carrier on a primarycell, the wireless device may be configured with an initial BWP forrandom access procedure on a secondary carrier.

A wireless device may expect that a center frequency for a DL BWP may besame as a center frequency for a UL BWP, for example, for unpairedspectrum operation. A base station may semi-statically configure awireless device for a cell with one or more parameters, for example, fora DL BWP or an UL BWP in a set of one or more DL BWPs or one or more ULBWPs, respectively. The one or more parameters may indicate one or moreof following: a subcarrier spacing; a cyclic prefix; a number ofcontiguous PRBs; an index in the set of one or more DL BWPs and/or oneor more UL BWPs; a link between a DL BWP and an UL BWP from a set ofconfigured DL BWPs and UL BWPs; a DCI detection to a PDSCH receptiontiming; a PDSCH reception to a HARQ-ACK transmission timing value; a DCIdetection to a PUSCH transmission timing value; and/or an offset of afirst PRB of a DL bandwidth or an UL bandwidth, respectively, relativeto a first PRB of a bandwidth.

For a DL BWP in a set of one or more DL BWPs on a PCell, a base stationmay configure a wireless device with one or more control resource setsfor at least one type of common search space and/or one wirelessdevice-specific search space. A base station may refrain fromconfiguring a wireless device without a common search space on a PCell,or on a PSCell, in an active DL BWP. For an UL BWP in a set of one ormore UL BWPs, a base station may configure a wireless device with one ormore resource sets for one or more PUCCH transmissions.

DCI may comprise a BWP indicator field. The BWP indicator field valuemay indicate an active DL BWP, from a configured DL BWP set, for one ormore DL receptions. The BWP indicator field value may indicate an activeUL BWP, from a configured UL BWP set, for one or more UL transmissions.

For a PCell, a base station may semi-statically configure a wirelessdevice with a default DL BWP among configured DL BWPs. If a wirelessdevice is not provided with a default DL BWP, a default BWP may be aninitial active DL BWP. A default BWP may not be configured for one ormore wireless devices. A first (or initial) BWP may serve as a defaultBWP, for example, if a default BWP is not configured.

A base station may configure a wireless device with a timer value for aPCell. A wireless device may start a timer (e.g., a BWP inactivitytimer), for example, if a wireless device detects DCI indicating anactive DL BWP, other than a default DL BWP, for a paired spectrumoperation, and/or if a wireless device detects DCI indicating an activeDL BWP or UL BWP, other than a default DL BWP or UL BWP, for an unpairedspectrum operation. The wireless device may increment the timer by aninterval of a first value (e.g., the first value may be 1 millisecond,0.5 milliseconds, or any other time duration), for example, if thewireless device does not detect DCI at (e.g., during) the interval for apaired spectrum operation or for an unpaired spectrum operation. Thetimer may expire at a time that the timer is equal to the timer value. Awireless device may switch to the default DL BWP from an active DL BWP,for example, if the timer expires.

A base station may semi-statically configure a wireless device with oneor more BWPs. A wireless device may switch an active BWP from a firstBWP to a second BWP, for example, after or in response to receiving DCIindicating the second BWP as an active BWP, and/or after or in responseto an expiry of BWP inactivity timer (e.g., the second BWP may be adefault BWP). FIG. 10 shows an example of three BWPs configured, BWP1(1010 and 1050), BWP2 (1020 and 1040), and BWP3 (1030). BWP2 (1020 and1040) may be a default BWP. BWP1 (1010) may be an initial active BWP. Awireless device may switch an active BWP from BWP1 1010 to BWP2 1020,for example, after or in response to an expiry of the BWP inactivitytimer. A wireless device may switch an active BWP from BWP2 1020 to BWP31030, for example, after or in response to receiving DCI indicating BWP31030 as an active BWP. Switching an active BWP from BWP3 1030 to BWP21040 and/or from BWP2 1040 to BWP1 1050 may be after or in response toreceiving DCI indicating an active BWP, and/or after or in response toan expiry of BWP inactivity timer.

Wireless device procedures on a secondary cell may be same as on aprimary cell using the timer value for the secondary cell and thedefault DL BWP for the secondary cell, for example, if a wireless deviceis configured for a secondary cell with a default DL BWP amongconfigured DL BWPs and a timer value. A wireless device may use anindicated DL BWP and an indicated UL BWP on a secondary cell as arespective first active DL BWP and first active UL BWP on a secondarycell or carrier, for example, if a base station configures a wirelessdevice with a first active DL BWP and a first active UL BWP on asecondary cell or carrier.

FIG. 11A and FIG. 11B show packet flows using a multi connectivity(e.g., dual connectivity, multi connectivity, tight interworking, and/orthe like). FIG. 11A shows an example of a protocol structure of awireless device 110 (e.g., UE) with CA and/or multi connectivity. FIG.11B shows an example of a protocol structure of multiple base stationswith CA and/or multi connectivity. The multiple base stations maycomprise a master node, MN 1130 (e.g., a master node, a master basestation, a master gNB, a master eNB, and/or the like) and a secondarynode, SN 1150 (e.g., a secondary node, a secondary base station, asecondary gNB, a secondary eNB, and/or the like). A master node 1130 anda secondary node 1150 may co-work to communicate with a wireless device110.

If multi connectivity is configured for a wireless device 110, thewireless device 110, which may support multiple reception and/ortransmission functions in an RRC connected state, may be configured toutilize radio resources provided by multiple schedulers of a multiplebase stations. Multiple base stations may be inter-connected via anon-ideal or ideal backhaul (e.g., Xn interface, X2 interface, and/orthe like). A base station involved in multi connectivity for a certainwireless device may perform at least one of two different roles: a basestation may act as a master base station or act as a secondary basestation. In multi connectivity, a wireless device may be connected toone master base station and one or more secondary base stations. Amaster base station (e.g., the MN 1130) may provide a master cell group(MCG) comprising a primary cell and/or one or more secondary cells for awireless device (e.g., the wireless device 110). A secondary basestation (e.g., the SN 1150) may provide a secondary cell group (SCG)comprising a primary secondary cell (PSCell) and/or one or moresecondary cells for a wireless device (e.g., the wireless device 110).

In multi connectivity, a radio protocol architecture that a bearer usesmay depend on how a bearer is setup. Three different types of bearersetup options may be supported: an MCG bearer, an SCG bearer, and/or asplit bearer. A wireless device may receive and/or send (e.g., transmit)packets of an MCG bearer via one or more cells of the MCG. A wirelessdevice may receive and/or send (e.g., transmit) packets of an SCG bearervia one or more cells of an SCG. Multi-connectivity may indicate havingat least one bearer configured to use radio resources provided by thesecondary base station. Multi-connectivity may or may not be configuredand/or implemented.

A wireless device (e.g., wireless device 110) may send (e.g., transmit)and/or receive: packets of an MCG bearer via an SDAP layer (e.g., SDAP1110), a PDCP layer (e.g., NR PDCP 1111), an RLC layer (e.g., MN RLC1114), and a MAC layer (e.g., MN MAC 1118); packets of a split bearervia an SDAP layer (e.g., SDAP 1110), a PDCP layer (e.g., NR PDCP 1112),one of a master or secondary RLC layer (e.g., MN RLC 1115, SN RLC 1116),and one of a master or secondary MAC layer (e.g., MN MAC 1118, SN MAC1119); and/or packets of an SCG bearer via an SDAP layer (e.g., SDAP1110), a PDCP layer (e.g., NR PDCP 1113), an RLC layer (e.g., SN RLC1117), and a MAC layer (e.g., MN MAC 1119).

A master base station (e.g., MN 1130) and/or a secondary base station(e.g., SN 1150) may send (e.g., transmit) and/or receive: packets of anMCG bearer via a master or secondary node SDAP layer (e.g., SDAP 1120,SDAP 1140), a master or secondary node PDCP layer (e.g., NR PDCP 1121,NR PDCP 1142), a master node RLC layer (e.g., MN RLC 1124, MN RLC 1125),and a master node MAC layer (e.g., MN MAC 1128); packets of an SCGbearer via a master or secondary node SDAP layer (e.g., SDAP 1120, SDAP1140), a master or secondary node PDCP layer (e.g., NR PDCP 1122, NRPDCP 1143), a secondary node RLC layer (e.g., SN RLC 1146, SN RLC 1147),and a secondary node MAC layer (e.g., SN MAC 1148); packets of a splitbearer via a master or secondary node SDAP layer (e.g., SDAP 1120, SDAP1140), a master or secondary node PDCP layer (e.g., NR PDCP 1123, NRPDCP 1141), a master or secondary node RLC layer (e.g., MN RLC 1126, SNRLC 1144, SN RLC 1145, MN RLC 1127), and a master or secondary node MAClayer (e.g., MN MAC 1128, SN MAC 1148).

In multi connectivity, a wireless device may configure multiple MACentities, such as one MAC entity (e.g., MN MAC 1118) for a master basestation, and other MAC entities (e.g., SN MAC 1119) for a secondary basestation. In multi-connectivity, a configured set of serving cells for awireless device may comprise two subsets: an MCG comprising servingcells of a master base station, and SCGs comprising serving cells of asecondary base station. For an SCG, one or more of followingconfigurations may be used. At least one cell of an SCG may have aconfigured UL CC and at least one cell of a SCG, named as primarysecondary cell (e.g., PSCell, PCell of SCG, PCell), and may beconfigured with PUCCH resources. If an SCG is configured, there may beat least one SCG bearer or one split bearer. After or upon detection ofa physical layer problem or a random access problem on a PSCell, or anumber of NR RLC retransmissions has been reached associated with theSCG, or after or upon detection of an access problem on a PSCellassociated with (e.g., during) a SCG addition or an SCG change: an RRCconnection re-establishment procedure may not be triggered, ULtransmissions towards cells of an SCG may be stopped, a master basestation may be informed by a wireless device of a SCG failure type, a DLdata transfer over a master base station may be maintained (e.g., for asplit bearer). An NR RLC acknowledged mode (AM) bearer may be configuredfor a split bearer. A PCell and/or a PSCell may not be de-activated. APSCell may be changed with a SCG change procedure (e.g., with securitykey change and a RACH procedure). A bearer type change between a splitbearer and a SCG bearer, and/or simultaneous configuration of a SCG anda split bearer, may or may not be supported.

With respect to interactions between a master base station and asecondary base stations for multi-connectivity, one or more of thefollowing may be used. A master base station and/or a secondary basestation may maintain Radio Resource Management (RRM) measurementconfigurations of a wireless device. A master base station may determine(e.g., based on received measurement reports, traffic conditions, and/orbearer types) to request a secondary base station to provide additionalresources (e.g., serving cells) for a wireless device. After or uponreceiving a request from a master base station, a secondary base stationmay create and/or modify a container that may result in a configurationof additional serving cells for a wireless device (or decide that thesecondary base station has no resource available to do so). For awireless device capability coordination, a master base station mayprovide (e.g., all or a part of) an AS configuration and wireless devicecapabilities to a secondary base station. A master base station and asecondary base station may exchange information about a wireless deviceconfiguration such as by using RRC containers (e.g., inter-nodemessages) carried via Xn messages. A secondary base station may initiatea reconfiguration of the secondary base station existing serving cells(e.g., PUCCH towards the secondary base station). A secondary basestation may decide which cell is a PSCell within a SCG. A master basestation may or may not change content of RRC configurations provided bya secondary base station. A master base station may provide recent(and/or the latest) measurement results for SCG cell(s), for example, ifan SCG addition and/or an SCG SCell addition occurs. A master basestation and secondary base stations may receive information of SFNand/or subframe offset of each other from an OAM and/or via an Xninterface (e.g., for a purpose of DRX alignment and/or identification ofa measurement gap). Dedicated RRC signaling may be used for sendingrequired system information of a cell as for CA, for example, if addinga new SCG SCell, except for an SFN acquired from an MIB of a PSCell of aSCG.

FIG. 12 shows an example of a random access procedure. One or moreevents may trigger a random access procedure. For example, one or moreevents may be at least one of following: initial access from RRC_IDLE,RRC connection re-establishment procedure, handover, DL or UL dataarrival in (e.g., during) a state of RRC_CONNECTED (e.g., if ULsynchronization status is non-synchronized), transition fromRRC_Inactive, and/or request for other system information. A PDCCHorder, a MAC entity, and/or a beam failure indication may initiate arandom access procedure.

A random access procedure may comprise or be one of at least acontention based random access procedure and/or a contention free randomaccess procedure. A contention based random access procedure maycomprise one or more Msg 1 1220 transmissions, one or more Msg2 1230transmissions, one or more Msg3 1240 transmissions, and contentionresolution 1250. A contention free random access procedure may compriseone or more Msg 1 1220 transmissions and one or more Msg2 1230transmissions. One or more of Msg 1 1220, Msg 2 1230, Msg 3 1240, and/orcontention resolution 1250 may be transmitted in the same step. Atwo-step random access procedure, for example, may comprise a firsttransmission (e.g., Msg A) and a second transmission (e.g., Msg B). Thefirst transmission (e.g., Msg A) may comprise transmitting, by awireless device (e.g., wireless device 110) to a base station (e.g.,base station 120), one or more messages indicating an equivalent and/orsimilar contents of Msg1 1220 and Msg3 1240 of a four-step random accessprocedure. The second transmission (e.g., Msg B) may comprisetransmitting, by the base station (e.g., base station 120) to a wirelessdevice (e.g., wireless device 110) after or in response to the firstmessage, one or more messages indicating an equivalent and/or similarcontent of Msg2 1230 and contention resolution 1250 of a four-steprandom access procedure.

A base station may send (e.g., transmit, unicast, multicast, broadcast,etc.), to a wireless device, a RACH configuration 1210 via one or morebeams. The RACH configuration 1210 may comprise one or more parametersindicating at least one of following: an available set of PRACHresources for a transmission of a random access preamble, initialpreamble power (e.g., random access preamble initial received targetpower), an RSRP threshold for a selection of a SS block andcorresponding PRACH resource, a power-ramping factor (e.g., randomaccess preamble power ramping step), a random access preamble index, amaximum number of preamble transmissions, preamble group A and group B,a threshold (e.g., message size) to determine the groups of randomaccess preambles, a set of one or more random access preambles for asystem information request and corresponding PRACH resource(s) (e.g., ifany), a set of one or more random access preambles for a beam failurerecovery procedure and corresponding PRACH resource(s) (e.g., if any), atime window to monitor RA response(s), a time window to monitorresponse(s) on a beam failure recovery procedure, and/or a contentionresolution timer.

The Msg1 1220 may comprise one or more transmissions of a random accesspreamble. For a contention based random access procedure, a wirelessdevice may select an SS block with an RSRP above the RSRP threshold. Ifrandom access preambles group B exists, a wireless device may select oneor more random access preambles from a group A or a group B, forexample, depending on a potential Msg3 1240 size. If a random accesspreambles group B does not exist, a wireless device may select the oneor more random access preambles from a group A. A wireless device mayselect a random access preamble index randomly (e.g., with equalprobability or a normal distribution) from one or more random accesspreambles associated with a selected group. If a base stationsemi-statically configures a wireless device with an association betweenrandom access preambles and SS blocks, the wireless device may select arandom access preamble index randomly with equal probability from one ormore random access preambles associated with a selected SS block and aselected group.

A wireless device may initiate a contention free random accessprocedure, for example, based on a beam failure indication from a lowerlayer. A base station may semi-statically configure a wireless devicewith one or more contention free PRACH resources for a beam failurerecovery procedure associated with at least one of SS blocks and/orCSI-RSs. A wireless device may select a random access preamble indexcorresponding to a selected SS block or a CSI-RS from a set of one ormore random access preambles for a beam failure recovery procedure, forexample, if at least one of the SS blocks with an RSRP above a firstRSRP threshold amongst associated SS blocks is available, and/or if atleast one of CSI-RSs with a RSRP above a second RSRP threshold amongstassociated CSI-RSs is available.

A wireless device may receive, from a base station, a random accesspreamble index via PDCCH or RRC for a contention free random accessprocedure. The wireless device may select a random access preambleindex, for example, if a base station does not configure a wirelessdevice with at least one contention free PRACH resource associated withSS blocks or CSI-RS. The wireless device may select the at least one SSblock and/or select a random access preamble corresponding to the atleast one SS block, for example, if a base station configures thewireless device with one or more contention free PRACH resourcesassociated with SS blocks and/or if at least one SS block with a RSRPabove a first RSRP threshold amongst associated SS blocks is available.The wireless device may select the at least one CSI-RS and/or select arandom access preamble corresponding to the at least one CSI-RS, forexample, if a base station configures a wireless device with one or morecontention free PRACH resources associated with CSI-RSs and/or if atleast one CSI-RS with a RSRP above a second RSPR threshold amongst theassociated CSI-RSs is available.

A wireless device may perform one or more Msg1 1220 transmissions, forexample, by sending (e.g., transmitting) the selected random accesspreamble. The wireless device may determine a PRACH occasion from one ormore PRACH occasions corresponding to a selected SS block, for example,if the wireless device selects an SS block and is configured with anassociation between one or more PRACH occasions and/or one or more SSblocks. The wireless device may determine a PRACH occasion from one ormore PRACH occasions corresponding to a selected CSI-RS, for example, ifthe wireless device selects a CSI-RS and is configured with anassociation between one or more PRACH occasions and one or more CSI-RSs.The wireless device may send (e.g., transmit), to a base station, aselected random access preamble via a selected PRACH occasions. Thewireless device may determine a transmit power for a transmission of aselected random access preamble at least based on an initial preamblepower and a power-ramping factor. The wireless device may determine anRA-RNTI associated with a selected PRACH occasion in which a selectedrandom access preamble is sent (e.g., transmitted). The wireless devicemay not determine an RA-RNTI for a beam failure recovery procedure. Thewireless device may determine an RA-RNTI at least based on an index of afirst OFDM symbol, an index of a first slot of a selected PRACHoccasions, and/or an uplink carrier index for a transmission of Msg11220.

A wireless device may receive, from a base station, a random accessresponse, Msg 2 1230. The wireless device may start a time window (e.g.,ra-ResponseWindow) to monitor a random access response. For a beamfailure recovery procedure, the base station may configure the wirelessdevice with a different time window (e.g., bfr-ResponseWindow) tomonitor response to on a beam failure recovery request. The wirelessdevice may start a time window (e.g., ra-ResponseWindow orbfr-ResponseWindow) at a start of a first PDCCH occasion, for example,after a fixed duration of one or more symbols from an end of a preambletransmission. If the wireless device sends (e.g., transmits) multiplepreambles, the wireless device may start a time window at a start of afirst PDCCH occasion after a fixed duration of one or more symbols froman end of a first preamble transmission. The wireless device may monitora PDCCH of a cell for at least one random access response identified bya RA-RNTI, or for at least one response to a beam failure recoveryrequest identified by a C-RNTI, at a time that a timer for a time windowis running.

A wireless device may determine that a reception of random accessresponse is successful, for example, if at least one random accessresponse comprises a random access preamble identifier corresponding toa random access preamble sent (e.g., transmitted) by the wirelessdevice. The wireless device may determine that the contention freerandom access procedure is successfully completed, for example, if areception of a random access response is successful. The wireless devicemay determine that a contention free random access procedure issuccessfully complete, for example, if a contention free random accessprocedure is triggered for a beam failure recovery request and if aPDCCH transmission is addressed to a C-RNTI. The wireless device maydetermine that the random access procedure is successfully completed,and may indicate a reception of an acknowledgement for a systeminformation request to upper layers, for example, if at least one randomaccess response comprises a random access preamble identifier. Thewireless device may stop sending (e.g., transmitting) remainingpreambles (if any) after or in response to a successful reception of acorresponding random access response, for example, if the wirelessdevice has signaled multiple preamble transmissions.

The wireless device may perform one or more Msg 3 1240 transmissions,for example, after or in response to a successful reception of randomaccess response (e.g., for a contention based random access procedure).The wireless device may adjust an uplink transmission timing, forexample, based on a timing advanced command indicated by a random accessresponse. The wireless device may send (e.g., transmit) one or moretransport blocks, for example, based on an uplink grant indicated by arandom access response. Subcarrier spacing for PUSCH transmission forMsg3 1240 may be provided by at least one higher layer (e.g., RRC)parameter. The wireless device may send (e.g., transmit) a random accesspreamble via a PRACH, and Msg3 1240 via PUSCH, on the same cell. A basestation may indicate an UL BWP for a PUSCH transmission of Msg3 1240 viasystem information block. The wireless device may use HARQ for aretransmission of Msg 3 1240.

Multiple wireless devices may perform Msg 1 1220, for example, bysending (e.g., transmitting) the same preamble to a base station. Themultiple wireless devices may receive, from the base station, the samerandom access response comprising an identity (e.g., TC-RNTI).Contention resolution (e.g., comprising the wireless device 110receiving contention resolution 1250) may be used to increase thelikelihood that a wireless device does not incorrectly use an identityof another wireless device. The contention resolution 1250 may be basedon, for example, a C-RNTI on a PDCCH, and/or a wireless devicecontention resolution identity on a DL-SCH. If a base station assigns aC-RNTI to a wireless device, the wireless device may perform contentionresolution (e.g., comprising receiving contention resolution 1250), forexample, based on a reception of a PDCCH transmission that is addressedto the C-RNTI. The wireless device may determine that contentionresolution is successful, and/or that a random access procedure issuccessfully completed, for example, after or in response to detecting aC-RNTI on a PDCCH. If a wireless device has no valid C-RNTI, acontention resolution may be addressed by using a TC-RNTI. If a MAC PDUis successfully decoded and a MAC PDU comprises a wireless devicecontention resolution identity MAC CE that matches or otherwisecorresponds with the CCCH SDU sent (e.g., transmitted) in Msg3 1250, thewireless device may determine that the contention resolution (e.g.,comprising contention resolution 1250) is successful and/or the wirelessdevice may determine that the random access procedure is successfullycompleted.

FIG. 13 shows an example structure for MAC entities. A wireless devicemay be configured to operate in a multi-connectivity mode. A wirelessdevice in RRC_CONNECTED with multiple Rx/Tx may be configured to utilizeradio resources provided by multiple schedulers that may be located in aplurality of base stations. The plurality of base stations may beconnected via a non-ideal or ideal backhaul over the Xn interface. Abase station in a plurality of base stations may act as a master basestation or as a secondary base station. A wireless device may beconnected to and/or in communication with, for example, one master basestation and one or more secondary base stations. A wireless device maybe configured with multiple MAC entities, for example, one MAC entityfor a master base station, and one or more other MAC entities forsecondary base station(s). A configured set of serving cells for awireless device may comprise two subsets: an MCG comprising servingcells of a master base station, and one or more SCGs comprising servingcells of a secondary base station(s). FIG. 13 shows an example structurefor MAC entities in which a MCG and a SCG are configured for a wirelessdevice.

At least one cell in a SCG may have a configured UL CC. A cell of the atleast one cell may comprise a PSCell or a PCell of a SCG, or a PCell. APSCell may be configured with PUCCH resources. There may be at least oneSCG bearer, or one split bearer, for a SCG that is configured. After orupon detection of a physical layer problem or a random access problem ona PSCell, after or upon reaching a number of RLC retransmissionsassociated with the SCG, and/or after or upon detection of an accessproblem on a PSCell associated with (e.g., during) a SCG addition or aSCG change: an RRC connection re-establishment procedure may not betriggered, UL transmissions towards cells of a SCG may be stopped,and/or a master base station may be informed by a wireless device of aSCG failure type and DL data transfer over a master base station may bemaintained.

A MAC sublayer may provide services such as data transfer and radioresource allocation to upper layers (e.g., 1310 or 1320). A MAC sublayermay comprise a plurality of MAC entities (e.g., 1350 and 1360). A MACsublayer may provide data transfer services on logical channels. Toaccommodate different kinds of data transfer services, multiple types oflogical channels may be defined. A logical channel may support transferof a particular type of information. A logical channel type may bedefined by what type of information (e.g., control or data) istransferred. BCCH, PCCH, CCCH and/or DCCH may be control channels, andDTCH may be a traffic channel. A first MAC entity (e.g., 1310) mayprovide services on PCCH, BCCH, CCCH, DCCH, DTCH, and/or MAC controlelements. A second MAC entity (e.g., 1320) may provide services on BCCH,DCCH, DTCH, and/or MAC control elements.

A MAC sublayer may expect from a physical layer (e.g., 1330 or 1340)services such as data transfer services, signaling of HARQ feedback,and/or signaling of scheduling request or measurements (e.g., CQI). Indual connectivity, two MAC entities may be configured for a wirelessdevice: one for a MCG and one for a SCG. A MAC entity of a wirelessdevice may handle a plurality of transport channels. A first MAC entitymay handle first transport channels comprising a PCCH of a MCG, a firstBCH of the MCG, one or more first DL-SCHs of the MCG, one or more firstUL-SCHs of the MCG, and/or one or more first RACHs of the MCG. A secondMAC entity may handle second transport channels comprising a second BCHof a SCG, one or more second DL-SCHs of the SCG, one or more secondUL-SCHs of the SCG, and/or one or more second RACHs of the SCG.

If a MAC entity is configured with one or more SCells, there may bemultiple DL-SCHs, multiple UL-SCHs, and/or multiple RACHs per MACentity. There may be one DL-SCH and/or one UL-SCH on an SpCell. Theremay be one DL-SCH, zero or one UL-SCH, and/or zero or one RACH for anSCell. A DL-SCH may support receptions using different numerologiesand/or TTI duration within a MAC entity. A UL-SCH may supporttransmissions using different numerologies and/or TTI duration withinthe MAC entity.

A MAC sublayer may support different functions. The MAC sublayer maycontrol these functions with a control (e.g., Control 1355 and/orControl 1365) element. Functions performed by a MAC entity may compriseone or more of: mapping between logical channels and transport channels(e.g., in uplink or downlink), multiplexing (e.g., (De-) Multiplexing1352 and/or (De-) Multiplexing 1362) of MAC SDUs from one or differentlogical channels onto transport blocks (TBs) to be delivered to thephysical layer on transport channels (e.g., in uplink), demultiplexing(e.g., (De-) Multiplexing 1352 and/or (De-) Multiplexing 1362) of MACSDUs to one or different logical channels from transport blocks (TBs)delivered from the physical layer on transport channels (e.g., indownlink), scheduling information reporting (e.g., in uplink), errorcorrection through HARQ in uplink and/or downlink (e.g., 1363), andlogical channel prioritization in uplink (e.g., Logical ChannelPrioritization 1351 and/or Logical Channel Prioritization 1361). A MACentity may handle a random access process (e.g., Random Access Control1354 and/or Random Access Control 1364).

FIG. 14 shows an example of a RAN architecture comprising one or morebase stations. A protocol stack (e.g., RRC, SDAP, PDCP, RLC, MAC, and/orPHY) may be supported at a node. A base station (e.g., gNB 120A and/or120B) may comprise a base station central unit (CU) (e.g., gNB-CU 1420Aor 1420B) and at least one base station distributed unit (DU) (e.g.,gNB-DU 1430A, 1430B, 1430C, and/or 1430D), for example, if a functionalsplit is configured. Upper protocol layers of a base station may belocated in a base station CU, and lower layers of the base station maybe located in the base station DUs. An F1 interface (e.g., CU-DUinterface) connecting a base station CU and base station DUs may be anideal or non-ideal backhaul. F1-C may provide a control plane connectionover an F1 interface, and F1-U may provide a user plane connection overthe F1 interface. An Xn interface may be configured between base stationCUs.

A base station CU may comprise an RRC function, an SDAP layer, and/or aPDCP layer. Base station DUs may comprise an RLC layer, a MAC layer,and/or a PHY layer. Various functional split options between a basestation CU and base station DUs may be possible, for example, bylocating different combinations of upper protocol layers (e.g., RANfunctions) in a base station CU and different combinations of lowerprotocol layers (e.g., RAN functions) in base station DUs. A functionalsplit may support flexibility to move protocol layers between a basestation CU and base station DUs, for example, depending on servicerequirements and/or network environments.

Functional split options may be configured per base station, per basestation CU, per base station DU, per wireless device, per bearer, perslice, and/or with other granularities. In a per base station CU split,a base station CU may have a fixed split option, and base station DUsmay be configured to match a split option of a base station CU. In a perbase station DU split, a base station DU may be configured with adifferent split option, and a base station CU may provide differentsplit options for different base station DUs. In a per wireless devicesplit, a base station (e.g., a base station CU and at least one basestation DUs) may provide different split options for different wirelessdevices. In a per bearer split, different split options may be utilizedfor different bearers. In a per slice splice, different split optionsmay be used for different slices.

FIG. 15 shows example RRC state transitions of a wireless device. Awireless device may be in at least one RRC state among an RRC connectedstate (e.g., RRC Connected 1530, RRC_Connected, etc.), an RRC idle state(e.g., RRC Idle 1510, RRC_Idle, etc.), and/or an RRC inactive state(e.g., RRC Inactive 1520, RRC_Inactive, etc.). In an RRC connectedstate, a wireless device may have at least one RRC connection with atleast one base station (e.g., gNB and/or eNB), which may have a contextof the wireless device (e.g., UE context). A wireless device context(e.g., UE context) may comprise at least one of an access stratumcontext, one or more radio link configuration parameters, bearer (e.g.,data radio bearer (DRB), signaling radio bearer (SRB), logical channel,QoS flow, PDU session, and/or the like) configuration information,security information, PHY/MAC/RLC/PDCP/SDAP layer configurationinformation, and/or the like configuration information for a wirelessdevice. In an RRC idle state, a wireless device may not have an RRCconnection with a base station, and a context of the wireless device maynot be stored in a base station. In an RRC inactive state, a wirelessdevice may not have an RRC connection with a base station. A context ofa wireless device may be stored in a base station, which may comprise ananchor base station (e.g., a last serving base station).

A wireless device may transition an RRC state (e.g., UE RRC state)between an RRC idle state and an RRC connected state in both ways (e.g.,connection release 1540 or connection establishment 1550; and/orconnection reestablishment) and/or between an RRC inactive state and anRRC connected state in both ways (e.g., connection inactivation 1570 orconnection resume 1580). A wireless device may transition its RRC statefrom an RRC inactive state to an RRC idle state (e.g., connectionrelease 1560).

An anchor base station may be a base station that may keep a context ofa wireless device (e.g., UE context) at least at (e.g., during) a timeperiod that the wireless device stays in a RAN notification area (RNA)of an anchor base station, and/or at (e.g., during) a time period thatthe wireless device stays in an RRC inactive state. An anchor basestation may comprise a base station that a wireless device in an RRCinactive state was most recently connected to in a latest RRC connectedstate, and/or a base station in which a wireless device most recentlyperformed an RNA update procedure. An RNA may comprise one or more cellsoperated by one or more base stations. A base station may belong to oneor more RNAs. A cell may belong to one or more RNAs.

A wireless device may transition, in a base station, an RRC state (e.g.,UE RRC state) from an RRC connected state to an RRC inactive state. Thewireless device may receive RNA information from the base station. RNAinformation may comprise at least one of an RNA identifier, one or morecell identifiers of one or more cells of an RNA, a base stationidentifier, an IP address of the base station, an AS context identifierof the wireless device, a resume identifier, and/or the like.

An anchor base station may broadcast a message (e.g., RAN pagingmessage) to base stations of an RNA to reach to a wireless device in anRRC inactive state. The base stations receiving the message from theanchor base station may broadcast and/or multicast another message(e.g., paging message) to wireless devices in their coverage area, cellcoverage area, and/or beam coverage area associated with the RNA via anair interface.

A wireless device may perform an RNA update (RNAU) procedure, forexample, if the wireless device is in an RRC inactive state and movesinto a new RNA. The RNAU procedure may comprise a random accessprocedure by the wireless device and/or a context retrieve procedure(e.g., UE context retrieve). A context retrieve procedure may comprise:receiving, by a base station from a wireless device, a random accesspreamble; and requesting and/or receiving (e.g., fetching), by a basestation, a context of the wireless device (e.g., UE context) from an oldanchor base station. The requesting and/or receiving (e.g., fetching)may comprise: sending a retrieve context request message (e.g., UEcontext request message) comprising a resume identifier to the oldanchor base station and receiving a retrieve context response messagecomprising the context of the wireless device from the old anchor basestation.

A wireless device in an RRC inactive state may select a cell to camp onbased on at least a measurement result for one or more cells, a cell inwhich a wireless device may monitor an RNA paging message, and/or a corenetwork paging message from a base station. A wireless device in an RRCinactive state may select a cell to perform a random access procedure toresume an RRC connection and/or to send (e.g., transmit) one or morepackets to a base station (e.g., to a network). The wireless device mayinitiate a random access procedure to perform an RNA update procedure,for example, if a cell selected belongs to a different RNA from an RNAfor the wireless device in an RRC inactive state. The wireless devicemay initiate a random access procedure to send (e.g., transmit) one ormore packets to a base station of a cell that the wireless deviceselects, for example, if the wireless device is in an RRC inactive stateand has one or more packets (e.g., in a buffer) to send (e.g., transmit)to a network. A random access procedure may be performed with twomessages (e.g., 2-stage or 2-step random access) and/or four messages(e.g., 4-stage or 4-step random access) between the wireless device andthe base station.

A base station receiving one or more uplink packets from a wirelessdevice in an RRC inactive state may request and/or receive (e.g., fetch)a context of a wireless device (e.g., UE context), for example, bysending (e.g., transmitting) a retrieve context request message for thewireless device to an anchor base station of the wireless device basedon at least one of an AS context identifier, an RNA identifier, a basestation identifier, a resume identifier, and/or a cell identifierreceived from the wireless device. A base station may send (e.g.,transmit) a path switch request for a wireless device to a core networkentity (e.g., AMF, MME, and/or the like), for example, after or inresponse to requesting and/or receiving (e.g., fetching) a context. Acore network entity may update a downlink tunnel endpoint identifier forone or more bearers established for the wireless device between a userplane core network entity (e.g., UPF, S-GW, and/or the like) and a RANnode (e.g., the base station), such as by changing a downlink tunnelendpoint identifier from an address of the anchor base station to anaddress of the base station).

A base station may communicate with a wireless device via a wirelessnetwork using one or more technologies, such as new radio technologies(e.g., NR, 5G, etc.). The one or more radio technologies may comprise atleast one of: multiple technologies related to physical layer; multipletechnologies related to medium access control layer; and/or multipletechnologies related to radio resource control layer Enhancing the oneor more radio technologies may improve performance of a wirelessnetwork. System throughput, and/or data rate of transmission, may beincreased. Battery consumption of a wireless device may be reduced.Latency of data transmission between a base station and a wirelessdevice may be improved. Network coverage of a wireless network may beimproved. Transmission efficiency of a wireless network may be improved.

A base station may send (e.g., transmit) DCI via a PDCCH for at leastone of: a scheduling assignment and/or grant; a slot formatnotification; a preemption indication; and/or a power-control command.The DCI may comprise at least one of: an identifier of a DCI format; adownlink scheduling assignment(s); an uplink scheduling grant(s); a slotformat indicator; a preemption indication; a power-control forPUCCH/PUSCH; and/or a power-control for SRS.

A downlink scheduling assignment DCI may comprise parameters indicatingat least one of: an identifier of a DCI format; a PDSCH resourceindication; a transport format; HARQ information; control informationrelated to multiple antenna schemes; and/or a command for power controlof the PUCCH. An uplink scheduling grant DCI may comprise parametersindicating at least one of: an identifier of a DCI format; a PUSCHresource indication; a transport format; HARQ related information;and/or a power control command of the PUSCH.

Different types of control information may correspond to different DCImessage sizes. Supporting multiple beams, spatial multiplexing in thespatial domain, and/or noncontiguous allocation of RBs in the frequencydomain, may require a larger scheduling message, in comparison with anuplink grant allowing for frequency-contiguous allocation. DCI may becategorized into different DCI formats. A DCI format may correspond to acertain message size and/or usage.

A wireless device may monitor (e.g., in common search space or wirelessdevice-specific search space) one or more PDCCH for detecting one ormore DCI with one or more DCI format. A wireless device may monitor aPDCCH with a limited set of DCI formats, for example, which may reducepower consumption. The more DCI formats that are to be detected, themore power may be consumed by the wireless device.

The information in the DCI formats for downlink scheduling may compriseat least one of: an identifier of a DCI format; a carrier indicator; anRB allocation; a time resource allocation; a bandwidth part indicator; aHARQ process number; one or more MCS; one or more NDI; one or more RV;MIMO related information; a downlink assignment index (DAI); a TPC forPUCCH; an SRS request; and/or padding (e.g., if necessary). The MIMOrelated information may comprise at least one of: a PMI; precodinginformation; a transport block swap flag; a power offset between PDSCHand a reference signal; a reference-signal scrambling sequence; a numberof layers; antenna ports for the transmission; and/or a transmissionconfiguration indication (TCI).

The information in the DCI formats used for uplink scheduling maycomprise at least one of: an identifier of a DCI format; a carrierindicator; a bandwidth part indication; a resource allocation type; anRB allocation; a time resource allocation; an MCS; an NDI; a phaserotation of the uplink DMRS; precoding information; a CSI request; anSRS request; an uplink index/DAI; a TPC for PUSCH; and/or padding (e.g.,if necessary).

A base station may perform CRC scrambling for DCI, for example, beforetransmitting the DCI via a PDCCH. The base station may perform CRCscrambling by binarily adding multiple bits of at least one wirelessdevice identifier (e.g., C-RNTI, CS-RNTI, TPC-CS-RNTI, TPC-PUCCH-RNTI,TPC-PUSCH-RNTI, SP CSI C-RNTI, and/or TPC-SRS-RNTI) on the CRC bits ofthe DCI. The wireless device may check the CRC bits of the DCI, forexample, if detecting the DCI. The wireless device may receive the DCI,for example, if the CRC is scrambled by a sequence of bits that is thesame as the at least one wireless device identifier.

A base station may send (e.g., transmit) one or more PDCCH in differentCORESETs, for example, to support a wide bandwidth operation. A basestation may transmit one or more RRC messages comprising configurationparameters of one or more CORESETs. A CORESET, of one or more CORESETs,may comprise at least one of: a first OFDM symbol; a number ofconsecutive OFDM symbols; a set of resource blocks; and/or a CCE-to-REGmapping. A base station may send (e.g., transmit) a PDCCH in a dedicatedCORESET for particular purpose, for example, for beam failure recoveryconfirmation. A wireless device may monitor a PDCCH for detecting DCI inone or more configured CORESETs, for example, to reduce the powerconsumption.

A base station may send (e.g., transmit) one or more MAC PDUs to awireless device. A MAC PDU may comprise a bit string that may be bytealigned (e.g., multiple of eight bits) in length. Bit strings may berepresented by tables in which the most significant bit is the leftmostbit of the first line of the table, and the least significant bit is therightmost bit on the last line of the table. The bit string may be readfrom the left to right, and then, in the reading order of the lines. Thebit order of a parameter field within a MAC PDU may be represented withthe first and most significant bit in the leftmost bit, and with thelast and least significant bit in the rightmost bit.

A MAC SDU may comprise a bit string that is byte aligned (e.g., multipleof eight bits) in length. A MAC SDU may be included in a MAC PDU, forexample, from the first bit onward. In an example, a MAC CE may be a bitstring that is byte aligned (e.g., multiple of eight bits) in length. AMAC subheader may be a bit string that is byte aligned (e.g., multipleof eight bits) in length. A MAC subheader may be placed immediately infront of the corresponding MAC SDU, MAC CE, and/or padding. A MAC entitymay ignore a value of reserved bits in a DL MAC PDU.

A MAC PDU may comprise one or more MAC subPDUs. A MAC subPDU of the oneor more MAC subPDUs may comprise at least one of: a MAC subheader only(e.g., including padding); a MAC subheader and a MAC SDU; a MACsubheader and a MAC CE; and/or a MAC subheader and padding. The MAC SDUmay be of variable size. A MAC subheader may correspond to a MAC SDU, aMAC CE, and/or padding.

A MAC subheader may comprise: an R field comprising one bit; an F fieldwith one bit in length; an LCID field with multiple bits in length; an Lfield with multiple bits in length, for example, if the MAC subheadercorresponds to a MAC SDU, a variable-sized MAC CE, and/or padding.

FIG. 16A shows an example of a MAC subheader comprising an eight-bit Lfield. The LCID field may have six bits in length. The L field may haveeight bits in length.

FIG. 16B shows an example of a MAC subheader with a sixteen-bit L field.The LCID field may have six bits in length. The L field may have sixteenbits in length. A MAC subheader may comprise: a R field comprising twobits in length; and an LCID field comprising multiple bits in length(e.g., if the MAC subheader corresponds to a fixed sized MAC CE), and/orpadding.

FIG. 16C shows an example of the MAC subheader. The LCID field maycomprise six bits in length, and the R field may comprise two bits inlength.

FIG. 17A shows an example of a DL MAC PDU. Multiple MAC CEs may beplaced together. A MAC subPDU comprising MAC CE may be placed before anyMAC subPDU comprising a MAC SDU, and/or before a MAC subPDU comprisingpadding.

FIG. 17B shows an example of a UL MAC PDU. Multiple MAC CEs may beplaced together. A MAC subPDU comprising a MAC CE may be placed afterall MAC subPDU comprising a MAC SDU. The MAC subPDU may be placed beforea MAC subPDU comprising padding.

FIG. 18 shows first examples of LCIDs. FIG. 19 shows second examples ofLCIDs. In each of FIG. 18 and FIG. 19 , the left columns compriseindices, and the right columns comprises corresponding LCID values foreach index.

FIG. 18 shows an example of an LCID that may be associated with the oneor more MAC CEs. A MAC entity of a base station may send (e.g.,transmit) to a MAC entity of a wireless device one or more MAC CEs. Theone or more MAC CEs may comprise at least one of: an SP ZP CSI-RSResource Set Activation/Deactivation MAC CE; a PUCCH spatial relationActivation/Deactivation MAC CE; a SP SRS Activation/Deactivation MAC CE;a SP CSI reporting on PUCCH Activation/Deactivation MAC CE; a TCI StateIndication for UE-specific PDCCH MAC CE; a TCI State Indication forUE-specific PDSCH MAC CE; an Aperiodic CSI Trigger State SubselectionMAC CE; a SP CSI-RS/CSI-IM Resource Set Activation/Deactivation MAC CE;a wireless device (e.g., UE) contention resolution identity MAC CE; atiming advance command MAC CE; a DRX command MAC CE; a long DRX commandMAC CE; an SCell activation and/or deactivation MAC CE (e.g., 1 Octet);an SCell activation and/or deactivation MAC CE (e.g., 4 Octet); and/or aduplication activation and/or deactivation MAC CE. A MAC CE may comprisean LCID in the corresponding MAC subheader. Different MAC CEs may havedifferent LCID in the corresponding MAC subheader. An LCID with 111011in a MAC subheader may indicate that a MAC CE associated with the MACsubheader is a long DRX command MAC CE.

FIG. 19 shows further examples of LCIDs associated with one or more MACCEs. The MAC entity of the wireless device may send (e.g., transmit), tothe MAC entity of the base station, one or more MAC CEs. The one or moreMAC CEs may comprise at least one of: a short buffer status report (BSR)MAC CE; a long BSR MAC CE; a C-RNTI MAC CE; a configured grantconfirmation MAC CE; a single entry power headroom report (PHR) MAC CE;a multiple entry PHR MAC CE; a short truncated BSR; and/or a longtruncated BSR. A MAC CE may comprise an LCID in the corresponding MACsubheader. Different MAC CEs may have different LCIDs in thecorresponding MAC subheader. The LCID with 111011 in a MAC subheader mayindicate that a MAC CE associated with the MAC subheader is ashort-truncated command MAC CE.

Two or more component carriers (CCs) may be aggregated, for example, ina carrier aggregation (CA). A wireless device may simultaneously receiveand/or transmit on one or more CCs, for example, depending oncapabilities of the wireless device. The CA may be supported forcontiguous CCs. The CA may be supported for non-contiguous CCs.

A wireless device may have one RRC connection with a network, forexample, if configured with CA. At (e.g., during) an RRC connectionestablishment, re-establishment and/or handover, a cell providing a NASmobility information may be a serving cell. At (e.g., during) an RRCconnection re-establishment and/or handover procedure, a cell providinga security input may be a serving cell. The serving cell may be referredto as a primary cell (PCell). A base station may send (e.g., transmit),to a wireless device, one or more messages comprising configurationparameters of a plurality of one or more secondary cells (SCells), forexample, depending on capabilities of the wireless device.

A base station and/or a wireless device may use an activation and/ordeactivation mechanism of an SCell for an efficient battery consumption,for example, if the base station and/or the wireless device isconfigured with CA. A base station may activate or deactivate at leastone of the one or more SCells, for example, if the wireless device isconfigured with one or more SCells. The SCell may be deactivated, forexample, after or upon configuration of an SCell.

A wireless device may activate and/or deactivate an SCell, for example,after or in response to receiving an SCell activation and/ordeactivation MAC CE. A base station may send (e.g., transmit), to awireless device, one or more messages comprising ansCellDeactivationTimer timer. The wireless device may deactivate anSCell, for example, after or in response to an expiry of thesCellDeactivationTimer timer.

A wireless device may activate an SCell, for example, if the wirelessdevice receives an SCell activation/deactivation MAC CE activating anSCell. The wireless device may perform operations (e.g., after or inresponse to the activating the SCell) that may comprise: SRStransmissions on the SCell; CQI, PMI, RI, and/or CRI reporting for theSCell on a PCell; PDCCH monitoring on the SCell; PDCCH monitoring forthe SCell on the PCell; and/or PUCCH transmissions on the SCell.

The wireless device may start and/or restart a timer (e.g., ansCellDeactivationTimer timer) associated with the SCell, for example,after or in response to activating the SCell. The wireless device maystart the timer (e.g., sCellDeactivationTimer timer) in the slot, forexample, if the SCell activation/deactivation MAC CE has been received.The wireless device may initialize and/or re-initialize one or moresuspended configured uplink grants of a configured grant Type 1associated with the SCell according to a stored configuration, forexample, after or in response to activating the SCell. The wirelessdevice may trigger a PHR, for example, after or in response toactivating the SCell.

The wireless device may deactivate the activated SCell, for example, ifthe wireless device receives an SCell activation/deactivation MAC CEdeactivating an activated SCell. The wireless device may deactivate theactivated SCell, for example, if a timer (e.g., ansCellDeactivationTimer timer) associated with an activated SCellexpires. The wireless device may stop the timer (e.g.,sCellDeactivationTimer timer) associated with the activated SCell, forexample, after or in response to deactivating the activated SCell. Thewireless device may clear one or more configured downlink assignmentsand/or one or more configured uplink grant Type 2 associated with theactivated SCell, for example, after or in response to the deactivatingthe activated SCell. The wireless device may suspend one or moreconfigured uplink grant Type 1 associated with the activated SCell,and/or flush HARQ buffers associated with the activated SCell, forexample, after or in response to deactivating the activated SCell.

A wireless device may refrain from performing certain operations, forexample, if an SCell is deactivated. The wireless device may refrainfrom performing one or more of the following operations if an SCell isdeactivated: transmitting SRS on the SCell; reporting CQI, PMI, RI,and/or CRI for the SCell on a PCell; transmitting on UL-SCH on theSCell; transmitting on a RACH on the SCell; monitoring at least onefirst PDCCH on the SCell; monitoring at least one second PDCCH for theSCell on the PCell; and/or transmitting a PUCCH on the SCell.

A wireless device may restart a timer (e.g., an sCellDeactivationTimertimer) associated with the activated SCell, for example, if at least onefirst PDCCH on an activated SCell indicates an uplink grant or adownlink assignment. A wireless device may restart a timer (e.g., ansCellDeactivationTimer timer) associated with the activated SCell, forexample, if at least one second PDCCH on a serving cell (e.g. a PCell oran SCell configured with PUCCH, such as a PUCCH SCell) scheduling theactivated SCell indicates an uplink grant and/or a downlink assignmentfor the activated SCell. A wireless device may abort the ongoing randomaccess procedure on the SCell, for example, if an SCell is deactivatedand/or if there is an ongoing random access procedure on the SCell.

FIG. 20A shows an example of an SCell activation/deactivation MAC CEthat may comprise one octet. A first MAC PDU subheader comprising afirst LCID may identify the SCell activation/deactivation MAC CE of oneoctet. An SCell activation/deactivation MAC CE of one octet may have afixed size. The SCell activation/deactivation MAC CE of one octet maycomprise a single octet. The single octet may comprise a first number ofC-fields (e.g., seven) and a second number of R-fields (e.g., one).

FIG. 20B shows an example of an SCell Activation/Deactivation MAC CE offour octets. A second MAC PDU subheader with a second LCID may identifythe SCell Activation/Deactivation MAC CE of four octets. An SCellactivation/deactivation MAC CE of four octets may have a fixed size. TheSCell activation/deactivation MAC CE of four octets may comprise fouroctets. The four octets may comprise a third number of C-fields (e.g.,31) and a fourth number of R-fields (e.g., 1). A C_(i) field mayindicate an activation/deactivation status of an SCell with an SCellindex i, for example, if an SCell with SCell index i is configured. AnSCell with an SCell index i may be activated, for example, if the C_(i)field is set to one. An SCell with an SCell index i may be deactivated,for example, if the C_(i) field is set to zero. The wireless device mayignore the C_(i) field, for example, if there is no SCell configuredwith SCell index i. An R field may indicate a reserved bit. The R fieldmay be set to zero.

A base station and/or a wireless device may use a power saving mechanism(e.g., hibernation mechanism) for an SCell, for example, if CA isconfigured. A power saving mechanism may improve battery performance(e.g., run-times), reduce power consumption of the wireless device,and/or to improve latency of SCell activation and/or SCell addition. TheSCell may be transitioned (e.g., switched and/or adjusted) to a dormantstate if the wireless device initiates a power saving state for (e.g.,hibernates) the SCell. The wireless device may, for example, if theSCell is transitioned to a dormant state: stop transmitting SRS on theSCell, report CQI/PMI/RI/PTI/CRI for the SCell according to or based ona periodicity configured for the SCell in a dormant state, not transmiton an UL-SCH on the SCell, not transmit on a RACH on the SCell, notmonitor the PDCCH on the SCell, not monitor the PDCCH for the SCell,and/or not transmit PUCCH on the SCell. Not transmitting, notmonitoring, not receiving, and/or not performing an action may comprise,for example, refraining from transmitting, refraining from monitoring,refraining from receiving, and/or refraining from performing an action,respectively. Reporting CSI for an SCell, that has been transitioned toa dormant state, and not monitoring the PDCCH on/for the SCell, mayprovide the base station an “always-updated” CSI for the SCell. The basestation may use a quick and/or accurate channel adaptive scheduling onthe SCell, based on the always-updated CSI, if the SCell is transitionedback to active state. Using the always-updated CSI may speed up anactivation procedure of the SCell. Reporting CSI for the SCell and notmonitoring the PDCCH on and/or for the SCell (e.g., that may have beentransitioned to a dormant state), may provide advantages such asincreased battery efficiency, reduced power consumption of the wirelessdevice, and/or increased timeliness and/or accuracy of channel feedbackinformation feedback. A PCell/PSCell and/or a PUCCH SCell, for example,may not be configured or transitioned to a dormant state.

A base station may activate, hibernate, or deactivate at least one ofone or more configured SCells. A base station may send (e.g., transmit)to a wireless device, for example, one or more messages comprisingparameters indicating at least one SCell being set to an active state, adormant state, or an inactive state. A base station may transmit, forexample, one or more RRC messages comprising parameters indicating atleast one SCell being set to an active state, a dormant state, or aninactive state. A base station may transmit, for example, one or moreMAC control elements (CEs) comprising parameters indicating at least oneSCell being set to an active state, a dormant state, or an inactivestate.

The wireless device may perform (e.g., if the SCell is in an activestate): SRS transmissions on the SCell, CQI/PMI/RI/CRI reporting for theSCell, PDCCH monitoring on the SCell, PDCCH monitoring for the SCell,and/or PUCCH/SPUCCH transmissions on the SCell. The wireless device may(e.g., if the SCell is in an inactive state): not transmit SRS on theSCell, not report CQI/PMI/RI/CRI for the SCell, not transmit on anUL-SCH on the SCell, not transmit on a RACH on the SCell, not monitorPDCCH on the SCell, not monitor a PDCCH for the SCell; and/or nottransmit a PUCCH/SPUCCH on the SCell. The wireless device may (e.g., ifthe SCell is in a dormant state): not transmit SRS on the SCell, reportCQI/PMI/RI/CRI for the SCell, not transmit on a UL-SCH on the SCell, nottransmit on a RACH on the SCell, not monitor a PDCCH on the SCell, notmonitor a PDCCH for the SCell, and/or not transmit a PUCCH/SPUCCH on theSCell.

A base station may send (e.g., transmit), for example, a first MAC CE(e.g., an activation/deactivation MAC CE). The first MAC CE mayindicate, to a wireless device, activation or deactivation of at leastone SCell. A C_(i) field may indicate an activation/deactivation statusof an SCell with an SCell index i, for example, if an SCell with SCellindex i is configured. An SCell with an SCell index i may be activated,for example, if the C_(i) field is set to one. An SCell with an SCellindex i may be deactivated, for example, if the C_(i) field is set tozero. A wireless device receiving a MAC CE may ignore the C_(i) field,for example, if there is no SCell configured with SCell index i. An Rfield may indicate a reserved bit. The R field may be set to zero.

A base station may transmit a MAC CE (e.g., a hibernation MAC CE) thatmay generally be referred to herein as a second MAC CE. The second MACCE may be the same as or different from other MAC CEs described herein,but is generally referred to herein as the second MAC CE. The second MACCE may indicate activation and/or hibernation of at least one SCell to awireless device. The second MAC CE may be associated with, for example,a second LCID different from a first LCID of the first MAC CE (e.g., theactivation/deactivation MAC CE). The second MAC CE may have a fixedsize. The second MAC CE may comprise a single octet comprising sevenC-fields and one R-field.

FIG. 21A shows an example of a MAC CE (e.g., the second MAC CEreferenced above) comprising a single octet. The second MAC CE maycomprise four octets comprising 31 C-fields and one R-field. FIG. 21Bshows an example of the second MAC CE comprising four octets. A secondMAC CE (e.g., comprising four octets) may be associated with a thirdLCID. The third LCID may be different from the second LCID for thesecond MAC CE and/or the first LCID for activation/deactivation MAC CE.The second MAC CE (e.g., comprising one octet) may be used, for example,if there is no SCell with a serving cell index greater than a value(e.g., 7 or any other value). The second MAC CE (e.g., comprising fouroctets) may be used, for example, if there is an SCell with a servingcell index greater than a value (e.g., 7 or any other value). A secondMAC CE may indicate a dormant/activated status of an SCell, for example,if a second MAC CE is received and a first MAC CE is not received. TheC_(i), field of the second MAC CE may indicate a dormant/activatedstatus of an SCell with SCell index i if there is an SCell configuredwith SCell index i, otherwise the MAC entity may ignore the C_(i),field. A wireless device may transition an SCell associated with SCellindex i into a dormant state, for example, if C_(i) of the second MAC CEis set to “1”. The wireless device may activate an SCell associated withSCell index i, for example, if C_(i), of the second MAC CE is set to“0”. The wireless device may activate the SCell with SCell index i, forexample, if C_(i), of the second MAC CE is set to “0” and the SCell withSCell index i is in a dormant state. The wireless device may ignore theC_(i) field of the second MAC CE, for example, if the C_(i) field is setto “0” and the SCell with SCell index i is not in a dormant state.

FIG. 21C shows example configurations of a field of the first MAC CE.The field may comprise, for example, a C_(i) field of the first MAC CE(e.g., an activation/deactivation MAC CE), a C_(i) field of the secondMAC CE (e.g., a hibernation MAC CE), and corresponding resulting SCellstatus (e.g., activated/deactivated/dormant). The wireless device maydeactivate an SCell associated with SCell index i, for example, ifC_(i), of hibernation MAC CE is set to 0, and C_(i) of theactivation/deactivation MAC CE is set to 0. The wireless device mayactivate an SCell associated with SCell index i, for example, if C_(i),of hibernation MAC CE is set to 0, and G of the activation/deactivationMAC CE is set to 1. The wireless device may ignore the hibernation MACCE and the activation/deactivation MAC CE, for example, if C_(i), ofhibernation MAC CE is set to 1, and C_(i), of theactivation/deactivation MAC CE is set to 0. The wireless device maytransition an SCell associated with SCell index I to a dormant state,for example, if C_(i), of hibernation MAC CE is set to 1, and C_(i), ofthe activation/deactivation MAC CE is set to 1.

FIG. 22 shows an example of SCell state transitions. The SCell statetransitions may be based on an activation/deactivation MAC CE and/or ahibernation MAC CE. A first MAC CE (e.g., activation/deactivation MACCE) and a second MAC CE (e.g., hibernation MAC CE) may indicate possiblestate transitions of the SCell with SCell index i if there is an SCellconfigured with SCell index i, and if both the first MAC CE and thesecond MAC CE are received, otherwise the MAC entity may ignore theC_(i) fields. The C_(i) fields of the two MAC CEs may be interpretedaccording to FIG. 21C. A first MAC CE (e.g., activation/deactivation MACCE) or a second MAC CE (e.g., hibernation MAC CE) may indicate possiblestate transitions of the SCell with SCell index i, for example, if thereis an SCell configured with SCell index i, and if one of the first MACCE and the second MAC CE is received. A MAC entity of a wireless devicemay, for example, deactivate an SCell, for example, if the MAC entityreceives a MAC CE(s) (e.g., activation/deactivation MAC CE) indicatingdeactivation of an SCell. The MAC entity may, based on the MAC CE(s):deactivate the SCell, stop an SCell deactivation timer associated withthe SCell, and/or flush all HARQ buffers associated with the SCell.

A base station may activate, hibernate, and/or deactivate at least oneof one or more SCells, for example, if the base station is configuredwith the one or more SCells. A MAC entity of a base station and/or awireless device may maintain an SCell deactivation timer (e.g.,sCellDeactivationTimer), for example, per a configured SCell and/orexcept for an SCell configured with PUCCH/SPUCCH, if any. The MAC entityof the base station and/or the wireless device may deactivate anassociated SCell, for example, if an SCell deactivation timer expires. AMAC entity of a base station and/or a wireless device may maintaindormant SCell deactivation timer (e.g., dormantSCellDeactivationTimer),for example, per a configured SCell and/or except for an SCellconfigured with PUCCH/SPUCCH, if any. The MAC entity of the base stationand/or the wireless device may deactivate an associated SCell, forexample, if the dormant SCell deactivation timer expires (e.g., if theSCell is in dormant state).

A MAC entity of a base station and/or a wireless device may, forexample, maintain an SCell hibernation timer (e.g.,sCellHibernationTimer), for example, per a configured SCell and/orexcept for an SCell configured with PUCCH/SPUCCH, if any. The MAC entityof the base station and/or the wireless device may hibernate anassociated SCell, for example, if the SCell hibernation timer expires(e.g., if the SCell is in active state). The SCell hibernation timer maytake priority over the SCell deactivation timer, for example, if boththe SCell deactivation timer and the SCell hibernation timer areconfigured. A base station and/or a wireless device may ignore the SCelldeactivation timer regardless of the SCell deactivation timer expiry,for example, if both the SCell deactivation timer and the SCellhibernation timer are configured.

FIG. 23 shows an example of SCell states (e.g., state transitions, stateswitching, etc.). The SCell state transitions may be based on, forexample, a first SCell timer (e.g., an SCell deactivation timer orsCellDeactivationTimer), a second SCell timer (e.g., an SCellhibernation timer or sCellHibernationTimer), and/or a third SCell timer(e.g., a dormant SCell deactivation timer ordormantSCellDeactivationTimer). A base station (e.g., a MAC entity of abase station) and/or a wireless device (e.g., a MAC entity of a wirelessdevice) may, for example, implement the SCell state transitions based onexpiration of the first SCell timer, the second SCell timer, and/or thethird SCell. The base station and/or the wireless device may, forexample, implement the SCell state transitions based on whether or not atimer (e.g., the second SCell timer) is configured. A base station(e.g., a MAC entity of a base station) and/or a wireless device (e.g., aMAC entity of a wireless device) may (e.g., if an SCell deactivationtimer expires and an SCell hibernation timer is not configured):deactivate an SCell, stop the SCell deactivation timer associated withthe SCell, and/or flush all HARQ buffers associated with the SCell.

A wireless device (e.g., MAC entity of a wireless device) may activatean SCell, for example, if the MAC entity is configured with an activatedSCell at SCell configuration. A wireless device (e.g., MAC entity of awireless device) may activate an SCell, for example, if the wirelessdevice receives a MAC CE(s) activating the SCell. The wireless device(e.g., MAC entity of a wireless device) may start or restart an SCelldeactivation timer associated with an SCell, for example, based on or inresponse to activating the SCell. The wireless device (e.g., MAC entityof a wireless device) may start or restart an SCell hibernation timer(e.g., if configured) associated with an SCell, for example, based on orin response to activating the SCell. A wireless device (e.g., MAC entityof a wireless device) may trigger a PHR procedure, for example, based onor in response to activating an SCell.

A wireless device (e.g., MAC entity of a wireless device) and/or a basestation (e.g., a MAC entity of a base station) may (e.g., if a firstPDCCH on an SCell indicates an uplink grant or downlink assignment, or asecond PDCCH on a serving cell scheduling the SCell indicates an uplinkgrant or a downlink assignment for the SCell, or a MAC PDU istransmitted in a configured uplink grant or received in a configureddownlink assignment) restart an SCell deactivation timer associated withan activated SCell and/or restart an SCell hibernation timer (e.g., ifconfigured) associated with the SCell. An ongoing random access (RA)procedure on an SCell may be aborted, for example, if, the SCell isdeactivated.

A wireless device (e.g., MAC entity of a wireless device) and/or a basestation (e.g., a MAC entity of a base station) may (e.g., if configuredwith an SCell associated with an SCell state set to dormant state uponthe SCell configuration, or if receiving MAC CE(s) indicatingtransitioning the SCell to a dormant state): set (e.g., transition) theSCell to a dormant state, transmit one or more CSI reports for theSCell, stop an SCell deactivation timer associated with the SCell, stopan SCell hibernation timer (if configured) associated with the SCell,start or restart a dormant SCell deactivation timer associated with theSCell, and/or flush all HARQ buffers associated with the SCell. Thewireless device (e.g., MAC entity of a wireless device) and/or a basestation (e.g., a MAC entity of a base station) may (e.g., if the SCellhibernation timer associated with the activated SCell expires):hibernate the SCell, stop the SCell deactivation timer associated withthe SCell, stop the SCell hibernation timer associated with the SCell,and/or flush all HARQ buffers associated with the SCell. The wirelessdevice (e.g., MAC entity of a wireless device) and/or a base station(e.g., a MAC entity of a base station) may (e.g., if a dormant SCelldeactivation timer associated with a dormant SCell expires): deactivatethe SCell and/or stop the dormant SCell deactivation timer associatedwith the SCell. Ongoing RA procedure on an SCell may be aborted, forexample, if the SCell is in dormant state.

A base station (e.g., a gNB) may configure a wireless device (e.g., aUE) with UL BWPs and DL BWPs to enable BA on a PCell. The base stationmay further configure the wireless device with at least DL BWP(s) (e.g.,there may be no UL BWPs in the UL) to enable BA on an SCell, if CA isconfigured. An initial active BWP may be a first BWP used for initialaccess, for example, for the PCell. A first active BWP may be a secondBWP configured for the wireless device to operate on the SCell, upon theSCell being activated. A base station and/or a wireless device mayindependently switch a DL BWP and an UL BWP, for example, if operatingin a paired spectrum (e.g., FDD). A base station and/or a wirelessdevice may simultaneously switch a DL BWP and an UL BWP, for example, ifoperating in an unpaired spectrum (e.g., TDD).

A base station and/or a wireless device may switch a BWP betweenconfigured BWPs, for example, based on a DCI or a BWP inactivity timer.A base station and/or a wireless device may switch an active BWP to adefault BWP, for example, based on or in response to an expiry of a BWPinactivity timer, if configured, associated with a serving cell. Thedefault BWP may be configured by the network.

One UL BWP for each uplink carrier and one DL BWP, for example, may beactive at a time in an active serving cell, for example, for FDD systemsthat are configured with BA. One DL/UL BWP pair, for example, may beactive at a time in an active serving cell, for example, for TDDsystems. Operating on the one UL BWP and the one DL BWP (or the oneDL/UL BWP pair) may, for example, improve wireless device batteryconsumption. BWPs other than the one active UL BWP and the one active DLBWP that the wireless device may work on may be deactivated. Ondeactivated BWPs, the wireless device may: not monitor PDCCH and/or nottransmit on a PUCCH, PRACH, and/or UL-SCH.

A serving cell may be configured with any number of BWPs (e.g., up tofour, or up to any other number of BWPs). There may be, for example, oneor any other number of active BWPs at any point in time for an activatedserving cell.

BWP switching for a serving cell may be used, for example, to activatean inactive BWP and/or deactivate an active BWP (e.g., at a time t). TheBWP switching may be controlled, for example, by a PDCCH indicating adownlink assignment and/or an uplink grant. The BWP switching may becontrolled, for example, by a BWP inactivity timer (e.g.,bwp-InactivityTimer). The BWP switching may be controlled, for example,by a MAC entity based on or in response to initiating an RA procedure.One or more BWPs may be initially active, without receiving a PDCCHindicating a downlink assignment or an uplink grant, for example, if anSpCell is added or an SCell is activated. The active BWP for a servingcell may be indicated by RRC message and/or PDCCH. A DL BWP may bepaired with an UL BWP, and BWP switching may be common for both UL andDL, for example, for unpaired spectrum.

FIG. 24 shows an example of BWP switching for an SCell. A base station2405 may send (e.g., transmit) one or more messages, to a wirelessdevice 2410. The one or more messages may be for configuring BWPscorresponding to the SCell 2415. The one or more messages may comprise,for example, one or more RRC messages (e.g., RRC connectionreconfiguration message, and/or RRC connection reestablishment message,and/or RRC connection setup message). The configured BWPs may compriseBWP 0, BWP 1, . . . BWP n. The BWP 0 may be configured as a default BWP.The BWP 1 may be configured as a first active BWP. At time n, the basestation 2405 may send (e.g., transmit) an RRC message and/or a MAC CEfor activating the SCell. At or after time n+k, and based on thereception of the RRC message and/or the MAC CE, the wireless device 2410may activate the SCell and start monitoring a PDCCH on the BWP 1 (e.g.,the first active BWP). At or after time m, the base station 2405 maysend (e.g., transmit) DCI for DL assignment or UL grant on the BWP 1. Ator after time m+1, the wireless device 2410 may receive a packet on theBWP 1 and may start a BWP inactivity timer (e.g., bwp-InactivityTimer).At time s, the BWP inactivity timer may expire. At or after time s+t, aBWP may switch to BWP 0 based on expiration of the BWP inactivity timer.BWP switching may comprise, for example, activating the BWP 0 anddeactivating the BWP 1. At time o, the base station 2405 may send (e.g.,transmit) an RRC message and/or a MAC CE for deactivating an SCell. Ator after time o+p, the wireless device 2410 may stop the BWP inactivitytimer and deactivate the SCell 2415.

A wireless device may receive RRC message comprising parameters of aSCell and one or more BWP configuration associated with the SCell. TheRRC message may comprise: RRC connection reconfiguration message (e.g.,RRCReconfiguration); RRC connection reestablishment message (e.g.,RRCRestablishment); and/or RRC connection setup message (e.g.,RRCSetup). Among the one or more BWPs, at least one BWP may beconfigured as the first active BWP (e.g., BWP 1 in FIG. 24 ), one BWP asthe default BWP (e.g., BWP 0 in FIG. 24 ). The wireless device mayreceive a MAC CE to activate the SCell at n^(th) slot. The wirelessdevice may start a SCell deactivation timer (e.g.,sCellDeactivationTimer), and start CSI related actions for the SCell,and/or start CSI related actions for the first active BWP of the SCell.The wireless device may start monitoring a PDCCH on BWP 1 in response toactivating the SCell.

The wireless device may start restart a BWP inactivity timer (e.g.,bwp-InactivityTimer) at m^(th) slot in response to receiving a DCIindicating DL assignment on BWP 1. The wireless device may switch backto the default BWP (e.g., BWP 0) as an active BWP when the BWPinactivity timer expires, at s^(th) slot. The wireless device maydeactivate the SCell and/or stop the BWP inactivity timer when thesCellDeactivationTimer expires.

Employing the BWP inactivity timer may further reduce a wirelessdevice's power consumption when the wireless device is configured withmultiple cells with each cell having wide bandwidth (e.g., 1 GHz). Thewireless device may only transmit on or receive from a narrow-bandwidthBWP (e.g., 5 MHz) on the PCell or SCell when there is no activity on anactive BWP.

A MAC entity may perform operations, on an active BWP for an activatedserving cell (e.g., configured with a BWP), comprising: transmitting onan UL-SCH; transmitting on a RACH, monitoring a PDCCH, transmitting on aPUCCH, receiving DL-SCH, and/or (re-) initializing any suspendedconfigured uplink grants of configured grant Type 1 according to astored configuration, if any. On an inactive BWP for each activatedserving cell configured with a BWP, a MAC entity may, for example: nottransmit on an UL-SCH, not transmit on a RACH, not monitor a PDCCH, nottransmit on a PUCCH, not transmit a SRS, not receive a DL-SCH, clear anyconfigured downlink assignment and configured uplink grant of configuredgrant Type 2, and/or suspend any configured uplink grant of configuredType 1. A wireless device may perform the BWP switching to a BWPindicated by the PDCCH, for example, if a MAC entity receives a PDCCHfor a BWP switching of a serving cell and a RA procedure associated withthis serving cell is not ongoing.

A bandwidth part indicator field value may indicate an active DL BWP,from a configured DL BWP set, for DL receptions for example, if thebandwidth part indicator field is configured in DCI format 1_1. Abandwidth part indicator field value, may indicate an active UL BWP,from a configured UL BWP set, for UL transmissions, for example, if thebandwidth part indicator field is configured in DCI format 0_1.

A wireless device may be provided by a higher layer parameter a timervalue corresponding to a BWP inactivity timer for the PCell (e.g.,bwp-InactivityTimer). The wireless device may increment the timer, ifrunning, for example, every interval of 1 millisecond (or any otherfirst duration) for frequency range 1 (or any other first frequencyrange) or every 0.5 milliseconds (or any other second duration) forfrequency range 2 (or any other second frequency range), for example,if: the wireless device does not detect DCI format 1_1 for pairedspectrum operation, or the wireless device does not detect DCI format1_1 or DCI format 0_1 for unpaired spectrum operation, during theinterval.

Wireless device procedures on an SCell may be similar to or the same asprocedures on a PCell, for example, if the wireless device is configuredfor the SCell with a higher layer parameter indicating a default DL BWPamong configured DL BWPs (e.g., Default-DL-BWP), and/or if the wirelessdevice is configured with a higher layer parameter indicating a timervalue (e.g., bwp-InactivityTimer). The wireless device procedures on theSCell may use the timer value for the SCell and the default DL BWP forthe SCell. The wireless device may use, as first active DL BWP and firstactive UL BWP on the SCell or secondary cell, an indicated DL BWP and anindicated UL BWP on the SCell, respectively, if a wireless device isconfigured, for example, by a higher layer parameter for the DL BWP(e.g., active-BWP-DL-SCell), and/or by a higher layer parameter for theUL BWP on the SCell or secondary cell (e.g., active-BWP-UL-SCell).

A wireless device may transmit one or more uplink control information(UCI) via one or more PUCCH resources to a base station. The wirelessdevice may transmit the one or more UCI, for example, as part of adiscontinuous reception (DRX) operation. The one or more UCI maycomprise at least one of: HARQ-ACK information; scheduling request (SR);and/or CSI report. A PUCCH resource may be identified by at least:frequency location (e.g., starting PRB); and/or a PUCCH formatassociated with initial cyclic shift of a base sequence and time domainlocation (e.g., starting symbol index). A PUCCH format may be PUCCHformat 0, PUCCH format 1, PUCCH format 2, PUCCH format 3, or PUCCHformat 4. A PUCCH format 0 may have a length of 1 or 2 OFDM symbols andbe less than or equal to 2 bits. A PUCCH format 1 may occupy a numberbetween 4 and 14 of OFDM symbols and be less than or equal to 2 bits. APUCCH format 2 may occupy 1 or 2 OFDM symbols and be greater than 2bits. A PUCCH format 3 may occupy a number between 4 and 14 of OFDMsymbols and be greater than 2 bits. A PUCCH format 4 may occupy a numberbetween 4 and 14 of OFDM symbols and be greater than 2 bits. The PUCCHresource may be configured on a PCell, or a PUCCH secondary cell.

If configured with multiple uplink BWPs, a base station may transmit toa wireless device, one or more RRC messages comprising configurationparameters of one or more PUCCH resource sets (e.g., at most 4 sets) onan uplink BWP of the multiple uplink BWPs. Each PUCCH resource set maybe configured with a PUCCH resource set index, a list of PUCCH resourceswith each PUCCH resource being identified by a PUCCH resource identifier(e.g., pucch-Resourceid), and/or a maximum number of UCI informationbits a wireless device may transmit using one of the plurality of PUCCHresources in the PUCCH resource set.

If configured with one or more PUCCH resource sets, a wireless devicemay select one of the one or more PUCCH resource sets based on a totalbit length of UCI information bits (e.g., HARQ-ARQ bits, SR, and/or CSI)the wireless device will transmit. In an example, when the total bitlength of UCI information bits is less than or equal to 2, the wirelessdevice may select a first PUCCH resource set with the PUCCH resource setindex equal to “0”. When the total bit length of UCI information bits isgreater than 2 and less than or equal to a first configured value, thewireless device may select a second PUCCH resource set with the PUCCHresource set index equal to “1”. When the total bit length of UCIinformation bits is greater than the first configured value and lessthan or equal to a second configured value, the wireless device mayselect a third PUCCH resource set with the PUCCH resource set indexequal to “2”. When the total bit length of UCI information bits isgreater than the second configured value and less than or equal to athird value (e.g., 1706), the wireless device may select a fourth PUCCHresource set with the PUCCH resource set index equal to “3”.

A wireless device may determine, based on a number of uplink symbols ofUCI transmission and a number of UCI bits, a PUCCH format from aplurality of PUCCH formats comprising PUCCH format 0, PUCCH format 1,PUCCH format 2, PUCCH format 3 and/or PUCCH format 4. The wirelessdevice may transmit UCI in a PUCCH using PUCCH format 0 if thetransmission is over 1 symbol or 2 symbols and the number of HARQ-ACKinformation bits with positive or negative SR (HARQ-ACK/SR bits) is 1 or2. The wireless device may transmit UCI in a PUCCH using PUCCH format 1if the transmission is over 4 or more symbols and the number ofHARQ-ACK/SR bits is 1 or 2. The wireless device may transmit UCI in aPUCCH using PUCCH format 2 if the transmission is over 1 symbol or 2symbols and the number of UCI bits is more than 2. The wireless devicemay transmit UCI in a PUCCH using PUCCH format 3 if the transmission isover 4 or more symbols, the number of UCI bits is more than 2 and PUCCHresource does not include an orthogonal cover code. The wireless devicemay transmit UCI in a PUCCH using PUCCH format 4 if the transmission isover 4 or more symbols, the number of UCI bits is more than 2 and thePUCCH resource includes an orthogonal cover code.

In order to transmit HARQ-ACK information on a PUCCH resource, awireless device may determine the PUCCH resource from a PUCCH resourceset. The PUCCH resource set may be determined as mentioned above. Thewireless device may determine the PUCCH resource based on a PUCCHresource indicator field in a DCI (e.g., with a DCI format 1_0 or DCIfor 1_1) received on a PDCCH. A 3-bit PUCCH resource indicator field inthe DCI may indicate one of eight PUCCH resources in the PUCCH resourceset. The wireless device may transmit the HARQ-ACK information in aPUCCH resource indicated by the 3-bit PUCCH resource indicator field inthe DCI.

The wireless device may transmit one or more UCI bits via a PUCCHresource of an active uplink BWP of a PCell or a PUCCH secondary cell.Since at most one active uplink BWP in a cell is supported for awireless device, the PUCCH resource indicated in the DCI is naturally aPUCCH resource on the active uplink BWP of the cell.

Discontinuous reception (DRX) operation may be used by a wirelessdevice, for example, to reduce power consumption, resource consumption(e.g., frequency and/or time resources), and/or improve battery lifetimeof the wireless device. A wireless device may discontinuously monitordownlink control channel (e.g., PDCCH or EPDCCH), for example, if thewireless device is operating using DRX. The base station may configureDRX operation with a set of DRX parameters. The base station mayconfigure the DRX operation using an RRC configuration. The set of DRXparameters may be selected (e.g., by the base station) based on anetwork use case. A wireless device may receive data packets over anextended delay, based on the configured DRX operation. The configuredDRX may be used such that a base station may wait, at least until thewireless device transitions to a DRX ON state, to receive data packets.The wireless device may be in a DRX Sleep/OFF state, for example, if notreceiving any data packets. The base station may select the DRXparameters, based on a consideration of a tradeoff between packet delayand power/resource conservation.

A wireless device that is configured with a DRX operation may power downat least some (or most) of its circuitry, for example, if there are nopackets to be received. The wireless device may monitor PDCCHdiscontinuously, for example, if DRX operation is configured. Thewireless device may monitor the PDCCH continuously, for example, if aDRX operation is not configured. The wireless device may listen toand/or monitor DL channels (e.g., PDCCHs) in a DRX active state, forexample, if DRX is configured. The wireless device may not listen toand/or monitor the DL channels (e.g., the PDCCHs) in a DRX Sleep state,for example, if DRX is configured.

FIG. 25 shows an example of a DRX operation. A base station (e.g., agNB) may transmit an RRC message 2502 comprising, for example, one ormore DRX parameters of a DRX cycle 2504. The RRC message may comprise:RRC connection reconfiguration message (e.g., RRCReconfiguration); RRCconnection reestablishment message (e.g., RRCRestablishment); and/or RRCconnection setup message (e.g., RRCSetup). The one or more parametersmay comprise, for example, a first parameter and/or a second parameter.The first parameter may indicate a first time value of a DRX activestate (e.g., DRX active/on duration 2508) of the DRX cycle 2504. Thesecond parameter may indicate a second time of a DRX sleep state (e.g.,DRX sleep/off duration 2512) of the DRX cycle 2504. The one or moreparameters may further comprise, for example, a time duration of the DRXcycle 2504.

The wireless device may monitor PDCCHs, for detecting one or more DCIson a serving cell, for example, if the wireless device is in the DRXactive state. The wireless device may stop monitoring PDCCHs on theserving cell, for example, if the wireless device is in the DRX sleepstate. The wireless device may monitor all PDCCHs on (or for) multiplecells that are in an active state, for example, if the wireless deviceis in the DRX active state. The wireless device may stop monitoring allPDCCH on (or for) the multiple cells, for example, if the wirelessdevice is in the DRX sleep state. The wireless device may repeat the DRXoperations according to the one or more DRX parameters.

DRX operation may be beneficial to a base station. A wireless device maytransmit periodic CSI and/or SRS frequently (e.g., based on aconfiguration), for example, if DRX is not configured. The wirelessdevice may not transmit periodic CSI and/or SRS in a DRX off period, forexample, if DRX is not configured. The base station may assign resourcesin DRX off period, that would otherwise be used for transmittingperiodic CSI and/or SRS, to the other wireless devices, for example, toimprove resource utilization efficiency.

A wireless device (e.g., a MAC entity of the wireless device) may beconfigured by RRC with a DRX functionality that controls downlinkcontrol channel (e.g., PDCCH) monitoring activity, of the wirelessdevice, for a plurality of RNTIs for the wireless device. The pluralityof RNTIs may comprise, for example, at least one of: C-RNTI, CS-RNTI,INT-RNTI, SP-CSI-RNTI, SFI-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI,Semi-Persistent Scheduling C-RNTI, eIMTA-RNTI, SL-RNTI, SL-V-RNTI,CC-RNTI, and/or SRS-TPC-RNTI. The wireless device (e.g., based on thewireless device being RRC_CONNECTED) may monitor the PDCCHdiscontinuously using a DRX operation, for example, if DRX isconfigured. The wireless device (e.g., the MAC entity of the wirelessdevice) may monitor the PDCCH continuously, for example, if DRX is notconfigured.

RRC may control DRX operation, for example, by configuring a pluralityof timers. The plurality of timers may comprise, for example: a DRX Onduration timer (e.g., drx-onDurationTimer), a DRX inactivity timer(e.g., drx-InactivityTimer), a downlink DRX HARQ RTT timer (e.g.,drx-HARQ-RTT-TimerDL), an uplink DRX HARQ RTT Timer (e.g.,drx-HARQ-RTT-TimerUL), a downlink retransmission timer (e.g.,drx-RetransmissionTimerDL), an uplink retransmission timer (e.g.,drx-RetransmissionTimerUL), one or more parameters of a short DRXconfiguration (e.g., drx-ShortCycle and/or drx-ShortCycleTimer)), and/orone or more parameters of a long DRX configuration (e.g.,drx-LongCycle). Time granularity for DRX timers may be defined in termsof PDCCH subframes (e.g., indicated as psf in DRX configurations), or interms of milliseconds.

An active time of a DRX cycle may include a time duration/period inwhich at least one timer is running. The at least one timer may comprisedrx-onDurationTimer, drx-InactivityTimer, drx-RetransmissionTimerDL,drx-RetransmissionTimerUL, or mac-ContentionResolutionTimer.

A drx-Inactivity-Timer may specify a time duration/period for which thewireless device may be active based on successfully decoding a PDCCHindicating a new transmission (UL or DL or SL). The drx-Inactivity-Timermay be restarted upon receiving PDCCH for a new transmission (UL or DLor SL). The wireless device may transition to a DRX mode (e.g., using ashort DRX cycle or a long DRX cycle), for example, based on the expiryof the drx-Inactivity-Timer.

A drx-ShortCycle may be a first type of DRX cycle (e.g., if configured)that may be followed, for example, if a wireless device enters DRX mode.A DRX-Config IE may indicate a length of the short cycle. Adrx-ShortCycleTimer may be expressed as multiples of shortDRX-Cycle. Thetimer may indicate a number of initial DRX cycles to follow the shortDRX cycle before entering a long DRX cycle.

A drx-onDurationTimer may specify, for example, a time duration at thebeginning of a DRX Cycle (e.g., DRX ON). The drx-onDurationTimer mayindicate, for example, a time duration before entering a sleep mode(e.g., DRX OFF).

A drx-HARQ-RTT-TimerDL may specify a minimum duration between a time atwhich a new transmission (e.g., a packet) is received and a time atwhich the wireless device may expect a retransmission (e.g., of thepacket). The drx-HARQ-RTT-TimerDL may be, for example, fixed and notconfigurable by RRC. A drx-RetransmissionTimerDL may indicate a maximumduration for which a wireless device may monitor PDCCH, for example, ifa retransmission from a base station is expected by the wireless device.

An active time of a configured DRX cycle may comprise, for example, atime at which a scheduling request (e.g., sent on PUCCH) is pending. Anactive time of a configured DXR cycle may comprise, for example, a timein which an uplink grant for a pending HARQ retransmission may occur,and in which data is present in a corresponding HARQ buffer for asynchronous HARQ process. An active time of a configured DRX cycle maycomprise, for example, a time in which a PDCCH indicating a newtransmission, addressed to the C-RNTI of the wireless device (e.g., aMAC entity of the wireless device), has not been received at thewireless device (e.g., after a successful reception of an RA response atthe wireless device). The RA response may correspond to, for example, aresponse to a preamble that is not selected by the wireless device,(e.g., the MAC entity of the wireless device).

A DL HARQ RTT timer may expire in a subframe and data of a correspondingHARQ process may not be successfully decoded, for example, at a wirelessdevice configured for DRX. A wireless device (e.g., a MAC entity of thewireless device) may start the drx-RetransmissionTimerDL for thecorresponding HARQ process. An UL HARQ RTT timer may expire in asubframe, for example, at a wireless device configured for DRX. Awireless device (e.g., a MAC entity of the wireless device) may startthe drx-RetransmissionTimerUL for a corresponding HARQ process. A DRXcommand MAC CE or a long DRX command MAC CE may be received, forexample, at a wireless device configured for DRX. A wireless device(e.g., a MAC entity of the wireless device) may stop thedrx-onDurationTimer and stop the drx-InactivityTimer.

A drx-InactivityTimer may expire or a DRX command MAC CE may be receivedin a subframe, for example, at a wireless device configured for DRX. Awireless device (e.g., a MAC entity of the wireless device) may start orrestart drx-ShortCycleTimer and may use a Short DRX Cycle, for example,if the Short DRX cycle is configured. The wireless device (e.g., the MACentity of the wireless device) may use a Long DRX cycle, if the long DRXcycle is configured.

A drx-ShortCycleTimer may expire in a subframe, for example, at awireless device configured for DRX. A wireless device (e.g., a MACentity of the wireless device) may use the long DRX cycle (e.g., basedon expiration of the drx-ShortCycleTimer). A long DRX command MAC CE maybe received. The wireless device (e.g., the MAC entity of the wirelessdevice) may stop a drx-ShortCycleTimer and may use the long DRX cycle(e.g., based on reception of the long DRX command MAC CE).

A wireless device that is configured for DRX operation may start adrx-onDurationTimer, for example, if the short DRX cycle is used and if[(SFN*10)+subframe number] modulo (drx-ShortCycle)=(drxStartOffset)modulo (drx-ShortCycle). A wireless device that is configured for DRXoperation may start a drx-onDurationTimer, for example, if the Long DRXCycle is used and if [(SFN*10)+subframe number] modulo(drx-longCycle)=drxStartOffset.

FIG. 26 shows example of DRX operation. A base station may send (e.g.,transmit) an RRC message to a wireless device. The RRC message maycomprise configuration parameters of DRX operation. The base station maysend (e.g., transmit), via a PDCCH, DCI for downlink resourceallocation, to the wireless device. The wireless device may start adrx-InactivityTimer and may monitor the PDCCH. The wireless device mayreceive a transmission block (TB), for example, while thedrx-InactivityTimer is running. The wireless device may start a HARQ RTTtimer (e.g., drx-HARQ-RTT-TimerDL), and may stop monitoring the PDCCH,for example, based on receiving the TB. The wireless device may transmita NACK to the base station, for example, if the wireless device fails toreceive the TB. The wireless device may monitor the PDCCH and start aHARQ retransmission timer (e.g., drx-RetransmissionTimerDL), forexample, based on an expiration of the HARQ RTT Timer. The wirelessdevice may receive second DCI, for example, while the HARQretransmission timer is running. The second DCI may indicate, forexample, a DL grant for a retransmission of the TB. The wireless devicemay stop monitoring the PDCCH, for example, if the wireless device failsto receive a second DCI before an expiration of the HARQ retransmissiontimer.

A wireless device may monitor PDCCH to detect DCI (e.g., one or more DCImessages) during a DRX active time of a DRX cycle, for example, if thewireless device is configured with DRX operation. The wireless devicemay stop monitoring PDCCH during the DRX sleep/off time of the DRXcycle, for example, to reduce power consumption. DCI (e.g., one or moreDCI messages) during a DRX active time of a DRX cycle may be addressedto other communication devices, different from the wireless device, forexample, in at least some DRX operations. The wireless device mayconsume power, for example, if the wireless device monitors the PDCCHduring the DRX active time of the DRX cycle, but the DCI (e.g., the oneor more DCI messages) is addressed to the other communication devices.In at least some communication systems, the wireless device may be, forexample, an ultra-reliable low-latency communication (URLLC) wirelessdevice, a narrowband internet of things (NB-IoT) wireless device, or amachine-type communication (MTC) wireless device. The wireless devicemay not always have data to be received from a base station. Waking upto monitor PDCCH in the DRX active time may result in wasted powerconsumption, for example, if there is no data to be received from thebase station. A wake-up mechanism may be combined with DRX operation,for example, to further reduce power consumption in a DRX active time.The wake-up mechanism may be used to selectively activate the wirelessdevice, for example, to be operational for a particular DRX cycle. Thewireless device may wake-up and monitor PDCCH to detect DCI (e.g., oneor more DCI messages) during a DRX active time of the particular DRXcycle.

In at least some communication systems, a wireless device may not beconfigured for DRX operation. The wake-up mechanism may be used toselectively activate the wireless device, for example, to be operationalfor a particular time period. The wake-up mechanism may be used toselectively activate the wireless device to continuously monitor PDCCHin a particular time period.

FIG. 27A and FIG. 27B show examples of a wake-up mechanism. In FIG. 27A,a base station may send (e.g., transmit) one or more messages 2702(e.g., RRC messages) comprising parameters of a wake-up duration 2704(or a power saving duration), to a wireless device. The wake-up durationmay be a number of slots (or symbols) before a DRX On duration 2706 of aDRX cycle. The number of slots (or symbols), or a gap, between thewake-up duration 2704 (e.g., an end of the wake-up duration) and the DRXOn duration 2706, may be configured in one or more RRC messages, or maybe a fixed and predefined value. The gap may be used for at least oneof: synchronization with the base station, measurement of referencesignals, and/or retuning of RF parameters. The gap may be determinedbased on capabilities of the wireless device and/or the base station.The wake-up mechanism may be based on a wake-up signal. The parametersof the wake-up duration 2704 may comprise at least one of: a wake-upsignal format (e.g., numerology, sequence length, sequence code, etc.),a periodicity of the wake-up signal, a time duration value of thewake-up duration, and/or a frequency location of the wake-up signal.

A wake-up signal for paging may comprise a signal sequence (e.g., aZadoff-Chu sequence) that is generated based on a cell identification(e.g., cell ID). The signal sequence may be, for

${{{example}:{w(m)}} = {{\theta_{n_{f},n_{s}}(m)} \cdot e^{- \frac{j\pi{{un}({n + 1})}}{131}}}},{{{wherein}m} = 0},1,{{{\ldots 132}M} - 1},{n = {m{mod}132}},$${\theta_{n_{f},n_{s}}(m)} = \left\{ {\begin{matrix}{1,{{{if}{c_{n_{f},n_{s}}\left( {2m} \right)}} = {{0{and}{c_{n_{f},n_{s}}\left( {{2m} + 1} \right)}} = 0}}} \\{{- 1},{{{if}{c_{n_{f},n_{s}}\left( {2m} \right)}} = {{0{and}{c_{n_{f},n_{s}}\left( {{2m} + 1} \right)}} = 1}}} \\{j,{{{if}{c_{n_{f},n_{s}}\left( {2m} \right)}} = {{1{and}{c_{n_{f},n_{s}}\left( {{2m} + 1} \right)}} = 0}}} \\{{- j},{{{if}{c_{n_{f},n_{s}}\left( {2m} \right)}} = {{1{and}{c_{n_{f},n_{s}}\left( {{2m} + 1} \right)}} = 1}}}\end{matrix},{{{and}u} = {\left( {N_{ID}^{cell}{mod}126} \right) +}}} \right.$

3. N_(ID) ^(cell) may be a cell ID of the serving cell. M may be anumber of subframes in which the wake-up signal may be transmitted. Mmay be bounded by a parameter, M_(WUSmax), such that 1≤M≤M_(WUSmax).M_(WUSmax) may be the maximum number of subframes in which the wake-upsignal may be transmitted. c_(n) _(f) _(,n) _(s) (i), i=0, 1, . . . ,2·132M−1 may be a scrambling sequence (e.g., a length-31 Gold sequence).The scrambling sequence may be initialized at a start of transmission ofthe wake-up with:

${{\left. {c_{{init}\_{WUS}} = {{\left( {N_{ID}^{cell} + 1} \right)\left( {{10n_{f\_{start}\_{PO}}} + \left\lfloor \frac{n_{s\_{start}\_{PO}}}{2} \right\rfloor} \right){mod}2048} + 1}} \right)2^{9}} + N_{ID}^{cell}},$

where n_(f_start_PO) may be a first frame of a first paging occasion towhich the wake-up signal is associated, and n_(s_start_PO) may be afirst slot of the first paging occasion to which the wake-up signal isassociated.

The parameters of the wake-up duration may be, for example, pre-definedwithout RRC configuration. The wake-up mechanism may be based on awake-up channel (e.g., a PDCCH, or DCI). The parameters of the wake-upduration may comprise at least one of: a wake-up channel format (e.g.,numerology, DCI format, PDCCH format), a periodicity of the wake-upchannel, a control resource set, and/or a search space of the wake-upchannel.

A wireless device may monitor a wake-up signal or a wake-up channelwithin the wake-up duration 2704 (e.g., as configured using one or moremessages 2702, or as predefined). The wireless device may wake-up tomonitor PDCCHs according to the DRX configuration, for example, based onreceiving a wake-up signal 2710 (e.g., via a wake-up channel) in thewake-up duration 2704. The wireless device may monitor PDCCHs in the DRXOn duration 2706, for example, based on receiving the wake-up signal2710. A drx-onDurationTimer may be running in the DRX On duration 2706.The wireless device may go to sleep if the wireless device fails toreceive PDCCHs in the DRX On duration 2706. The wireless device may bein a sleep state in a DRX Off duration 2708 of the DRX cycle. Thewireless device may fail to receive a wake-up signal in a wake-upduration 2712. The wireless device may skip monitoring (e.g., refrainfrom monitoring) PDCCHs in the DRX On duration 2714, for example, if thewireless device fails to receive a wake-up signal in the wake-upduration 2712. Skipping PDCCH monitoring, in the DRX On duration 2714,may reduce power consumption at the wireless device.

The wireless device may monitor the wake-up signal/channel only, forexample, in the wake-up duration 2704 or in the wake-up duration 2712.The wireless device may stop monitoring PDCCHs and the wake-up signal,for example, in the DRX Off duration 2708. The wireless device maymonitor PDCCHs in the DRX On duration 2706, for example, if the wirelessdevice receives the wake-up signal 2710 in the wake-up duration 2704.The wireless device may skip monitoring (e.g., refrain from monitoring)PDCCHs in the DRX On duration 2714, for example, if the wireless devicedoes not receive a wake-up signal in the wake-up duration 2712. The basestation and/or the wireless device may apply the wake-up mechanism inpaging operation, for example, if the wireless device is in an RRC=Idlestate or an RRC_inactive state. The base station and/or the wirelessdevice may apply the wake-up mechanism in paging operation, for example,in a connected DRX operation (C-DRX) if the wireless device is in anRRC_CONNECTED state.

A wake-up mechanism may be based on a go-to-sleep signal/channel. InFIG. 27B, a base station may send (e.g., transmit) one or more messages2750 (e.g., RRC messages). The one or more RRC messages may comprisingparameter of a wake-up duration 2752 (or a power saving duration), to awireless device. The one or more messages may comprise at least one RRCmessage. The at least one RRC message may comprise one or morecell-specific or cell-common RRC messages (e.g., ServingCellConfig IE,ServingCellConfigCommon IE, MAC-CellGroupConfig IE). The at least oneRRC message may comprise: RRC connection reconfiguration message (e.g.,RRCReconfiguration); RRC connection reestablishment message (e.g.,RRCRestablishment); and/or RRC connection setup message (e.g.,RRCSetup). The wake-up duration 2752 may be located a number of slots(or symbols) before a DRX On duration 2754 of a DRX cycle. The number ofslots (or symbols) may be configured in one or more RRC messages, or maybe a fixed and predefined value. The wake-up mechanism may be based on ago-to-sleep signal. The parameters of the wake-up duration 2752 maycomprise at least one of: a go-to-sleep signal format (e.g., numerology,sequence length, sequence code, etc.), a periodicity of the go-to-sleepsignal, a time duration value of the wake-up duration, and/or afrequency location of the go-to-sleep signal. The wake-up mechanism maybe based on a go-to-sleep channel (e.g., a PDCCH, or DCI). Theparameters of the wake-up duration may comprise at least one of: ago-to-sleep channel format (e.g., numerology, DCI format, PDCCH format),a periodicity of the go-to-sleep channel, and/or a control resource setand/or a search space of the go-to-sleep channel.

The wireless device may monitor the go-to-sleep signal or thego-to-sleep channel during the wake-up duration 2752, for example, ifthe wireless device is configured with the parameters of the wake-upduration 2752. The wireless device may go to sleep and skip monitoring(e.g., refrain from monitoring) PDCCHs in the DRX On duration 2754, forexample, if the wireless device receives the go-to-sleep signal 2756(e.g., via the go-to-sleep channel). The wireless device may be in asleep state in a DRX Off duration 2758, and may skip monitoring PDCCHsin the DRX Off duration 2758. The wireless device may monitor PDCCHs ina DRX On duration 2762, for example, if the wireless device fails toreceive a go-to-sleep signal in a wake-up duration 2760. Refraining fromPDCCH monitoring, in the DRX On duration 2754, may reduce powerconsumption at the wireless device.

In at least some communication systems, a go-to-sleep signal-basedwake-up mechanism may be more robust to detection error, for example, ascompared to a wake-up signal-based wake-up mechanism. A wireless devicemay miss DCI which may be addressed to the wireless device, for example,if the wireless device fails to detect a wake-up signal in a wake-upsignal-based wake-up mechanism. Missing the DCI may result ininterruption of communication, for example, between the wireless deviceand a base station. A wireless device may wrongly start monitoringPDCCH, for example, if the wireless device fails to detect a go-to-sleepsignal in the go-to-sleep signal-based wake-up mechanism. Wrongfulmonitoring of PDCCH may result in extra power consumption at thewireless device, but communication may still be maintained between thewireless device and a base station. In at least some communicationsystems (e.g., URLLC services or vehicle-to-everything, V2X, services),extra power consumption may be more acceptable than interruption ofcommunication between the wireless device and/or the base station.

In at least some systems, a base station and/or a wireless device mayperform a wake-up operation for power saving purpose. The base stationand/or the wireless device may use wake-up protocols, for example, ifthe base station and/or the wireless device are implementingcommunication technologies corresponding machine-type-communication(e.g., MTC) and/or narrow band internet of things (e.g., NB-IOT). Awake-up operation may be applicable for a system operating on a singlecarrier (e.g., wherein communication occurs on the single carrier), orfor a system operating on a plurality of carriers (e.g., whereincommunication occurs on the plurality of carriers). A wake-up operationmay comprise, for example, at least one of: transmitting, from a basestation and in a configured/predefined time and frequency resource, awake-up signal; monitoring, by a wireless device, the wake-up signal;monitoring, by the wireless device, PDCCH if the wireless devicereceives the wake-up signal; or the wireless device skipping monitoringthe PDCCH if the wireless device fails to receive the wake-up signal.The wake-up signal may comprise a signal sequence (e.g., a Zadoff-Chusequence, or an M sequence) that may be generated based on a cell ID ofa serving cell. The base station may transmit the wake-up signal with asame antenna port as a CRS (Cell-specific Reference signal) port, forexample, if a single CRS port is configured by the base station.

In at least some communication systems (e.g., a first communicationsystem), a base station and/or a wireless device may not perform awake-up operation for power saving purposes. The base station and/or awireless device may not perform a wake-up operation for example, if thewireless device is not an MTC-capable and/or NB-IOT-capable wirelessdevice. In at least some communication systems (e.g., the firstcommunication system), a base station and/or a wireless device may notperform a wake-up operation for power saving purposes, for example, ifthe wireless device communicates with the base station on multipleactive cells in a carrier aggregation mode.

In at least some communication systems, a wireless device that isconfigured with multiple cells may spend higher power consumption andmore flexible operation than a wireless device operating in the firstcommunication system. The wireless device may communicate with a basestation on cells using high frequency bands (e.g., 6 GHz, 30 GHz, or 70GHz), with higher power consumption than wireless devices operating inlower frequencies (e.g., <=6 GHz). In at least some communicationsystems, a base station may transmit to, and/or receive from a wirelessdevice, data packets corresponding to a plurality of data services(e.g., web browsing, video streaming, industry IoT, and/or communicationservices for automation in a variety of vertical domains). The pluralityof data services may have different data traffic patterns. Data trafficfor different data services may be periodic or aperiodic. Data arrivalpatterns may be different for different data services. Different dataservices may use different event-triggers and/or data sizes. Some dataservices may transmit using burst-type data traffic and some dataservices transmit using continuous data traffic.

A first data service may use, for example, a predicable/periodic trafficpattern that is suitable for power-saving based communication (e.g.,wake-up signaling and/or DRX-based operation). A second data service mayuse, for example, a continuous/non-predicable traffic pattern that isnot suitable for power-saving based communication. Using RRC signalingto switch between a power saving-based communication for the first dataservice (e.g., power saving mode/state) and non-power saving-basedcommunication for a second data service (e.g., normal access mode/state)may not be flexible or dynamic. Using RRC signaling to switch betweenthe power saving-based communication and the non-power saving-basedcommunication may result in, for example, increased latency and higherpower consumption (e.g., at a wireless device). A mechanism tosemi-statically and/or dynamically switch between a power saving basedcommunication and a non-power-saving based communication may bebeneficial for improved communication services (e.g., faster datatransfer speeds, reduced power consumption at a wireless device).

In at least some communication systems, different services withcorresponding different service requirements may be supported. One ormore power saving configurations may be used corresponding to thedifferent service requirements. Different power saving configurations(e.g., power saving operation configurations) may be used, for example,at a wireless device for the different services/service requirements.Using RRC signaling to support the different power saving operationconfigurations and/or to enable/disable power saving-based communicationmay not be flexible or dynamic. Using RRC signaling to switch betweenthe different power saving operation configurations may result in, forexample, increased latency and higher power consumption (e.g., at awireless device). A mechanism to support the different power savingoperation configurations, and/or to semi-statically/dynamically switchbetween the different power saving based operation configurations and/ornon-power-saving based communication may be beneficial for improvedcommunication services (e.g., faster data transfer speeds, reduced powerconsumption at a wireless device).

In at least some communication systems, one or more power savingoperation configurations may be used. The one or more power savingoperation configurations may comprise configurations corresponding to atleast one power saving mode (e.g., state). A wireless device may switchbetween a normal access mode and a power saving mode. The wirelessdevice in a power saving mode may, for example, use a power savingoperation configuration in the one or more of power saving operationconfigurations. The wireless device in a normal access mode may, forexample, disable the use of a power saving operation configuration. Apower saving operation may be performed based on parameters of a powersaving operation configuration. The parameters of a power savingoperation configuration may comprise at least one of: a duration of thepower saving operation, radio resources of transmission of a wake-upsignal for the power saving operation, and/or one or more timer valuesof one or more timers of the power saving operation. The parameters of apower saving operation configuration may comprise at least one of: aPDCCH monitoring periodicity, one or more configuration parameters of apower saving channel of the power saving operation configuration, anindication to cease PUSCH transmission(s), an indication to cease PUCCHtransmission(s), an indication to cease SRS transmission(s), anindication to cease an RACH procedure, and/or an indication to continueRRM/CSI/beam reporting. The one or more configuration parameters of thepower saving channel may indicate at least one of: a timing window formonitoring the power saving channel, a control resource set for thepower saving channel, and/or a RNTI for monitoring the power savingchannel.

At least one power saving operation configuration, of a plurality ofpower saving operation configurations, may be activated/deactivated fortransmission and/or reception of data corresponding to an ongoing dataservice. An activation/deactivation procedure of the at least one powersaving operation configuration may comprise at least one of:transmission/reception of an activation/deactivation command of a powersaving operation configuration and/or configuration of a power savingtimer.

A base station may transmit a command (e.g., DCI or a MAC CE) indicatinga power saving operation configuration of a plurality of power savingoperation configurations that will be activated. The command mayindicate a cell, of a plurality of cells, where the power savingoperation configuration is activated. A wireless device may applyparameters of the power saving operation configuration on the cellindicated by the command, for example, based on receiving the command.The wireless device, based on the parameters, may reduce/increase PDCCHmonitoring duration, stop/perform uplink transmission, therefore improvepower consumption, or data transmission latency.

FIG. 28 shows an example of an activation/deactivation of a power savingoperation configuration of one or more power saving operationconfigurations. A base station 2802 may send (e.g., transmit), to awireless device 2804, one or more RRC messages. The one or more RRCmessages may comprise configuration parameters of one or more cells. Thewireless device 2804 may receive the one or more RRC messages at timet₁. The one or more RRC messages may comprise, for example, one or morecell-specific or cell-common RRC messages (e.g., ServingCellConfig IE,ServingCellConfigCommon IE, MAC-CellGroupConfig IE, etc.). The cell maybe a primary cell (e.g., PCell), a PUCCH secondary cell (e.g., ifsecondary PUCCH group is configured), or a PSCell (e.g., if dualconnectivity is configured). The cell may be associated with (e.g.,indicated by) a cell specific identity (e.g., a cell ID). Theconfiguration parameters may comprise parameters of at least one powersaving operation (e.g., procedure, mode, and/or state) configuration onthe cell. Each power saving operation configuration of the at least onepower saving operation configuration may be identified by a power savingconfiguration identifier (e.g., an index, an indicator, or an ID).

A power saving operation corresponding to a power saving operationconfiguration may be based on a power saving signal (e.g., the wake-upsignal 2710 as shown in FIG. 27A, and/or a go-to-sleep 2756 as shown inFIG. 27B). The parameters of a power saving signal-based power savingoperation configuration may comprise, for example, at least one of: asignal format (e.g., numerology) of the power saving signal, sequencegeneration parameters (e.g., a cell ID, a virtual cell ID, SS blockindex, and/or an orthogonal code index) for generating the power savingsignal, a window size of a time window indicating a duration in whichthe power saving signal may be transmitted, a value of a periodicity ofthe transmission of the power saving signal, a time resource on whichthe power saving signal may be transmitted, a frequency resource onwhich the power saving signal may be transmitted, a BWP on which thewireless device 2804 may monitor the power saving signal, and/or a cellon which the wireless device 2804 may monitor the power saving signal.The power saving signal may comprise, for example, at least one of: anSS block, a CSI-RS, a DMRS, and/or a signal sequence (e.g., aZadoff-Chu, an M sequence, or a Gold sequence). A first power savingsignal-based power saving operation configuration for a first service(or an application such as enhanced Mobile Broadband, eMBB) may bedifferent from a second power saving signal-based power saving operationconfiguration for a second service (or an application such as massiveMTC, mMTC).

A power saving operation may be based on a power saving channel (e.g., awake-up channel (WUCH)). The power saving channel may comprise adownlink control channel (e.g., a PDCCH) dedicated for the power savingoperation. The parameters of a power saving channel-based power savingoperation configuration may comprise, for example, at least one of: atime window indicating a duration in which the base station 2802 maytransmit power saving information (e.g., a wake-up information, or ago-to-sleep information) via the power saving channel, parameters of acontrol resource set (e.g., time, frequency resource and/or TCI stateindication of the power saving channel), a periodicity of thetransmission of the power saving channel, a DCI format of the powersaving information, a BWP on which the wireless device 2804 may monitorthe power saving channel, and/or a cell on which the wireless device2804 may monitor the power saving channel. A first power savingchannel-based power saving operation configuration for a first servicemay be different from a second power saving channel-based power savingoperation configuration for a second service. The one or more RRCmessages may further comprise one or more DRX parameters of a DRXoperation. The one or more DRX parameters may comprise, for example, atleast one of: parameters of a short DRX cycle, parameters of a long DRXcycle, and/or one or more DRX timer values for one or more DRX timers(e.g., drx-onDurationTimer, drx-InactivityTimer,drxRetransmissionTimerDL, drxRetransmissionTimerUL,drx-HARQ-RTT-TimerDL, and/or drx-HARQ-RTT-TimerUL).

The wireless device (e.g., based on an RRC configuration) maycommunicate with a base station in a normal (e.g., full) access mode(e.g., state), for example, based on an RRC configuration. The wirelessdevice 2804 may communicate with the base station 2802 in the normalaccess mode, for example, based on the received one or more RRCmessages. The wireless device may monitor PDCCHs continuously, forexample, if a DRX operation is not configured for the wireless device inthe normal access mode. The wireless device may monitor the PDCCHsdiscontinuously by applying one or more DRX parameters of a DRXoperation, for example, if the DRX operation is configured (e.g., asshown in FIG. 25 ) for the wireless device in a normal access mode. Thewireless device may (e.g., in the normal access mode): transmit an SRS,transmit via a RACH, transmit via a UL-SCH, and/or receive via a DL-SCH.

The base station 2802 may trigger the wireless device 2804 (e.g., usingone or more messages, such as DCI messages and/or MAC CE messages) toswitch to a power saving mode (or a power efficient mode) from thenormal access mode. The base station 2802 may trigger the wirelessdevice 2804 to switch to the power saving mode, for example, if a dataservice that is suitable for the power saving mode is launched. Thewireless device 2804 may switch to the power saving mode, from thenormal access mode, for power conservation. The wireless device 2804 may(e.g., in the power saving mode): monitor for a power savingsignal/channel; not transmit (e.g., refrain from transmitting) PUCCH,PUSCH, SRS, and/or PRACH without detecting/receiving the power savingsignal; not receive PDSCH without detecting/receiving the power savingsignal; not monitor (e.g., refrain from monitoring) PDCCH withoutdetecting/receiving the power saving signal; and/or start monitoring thePDCCHs based on detecting/receiving the power saving signal/channel

The wireless device 2804 may send (e.g., transmit) one or moreindicators to the base station 2802 indicating a mode (e.g., the powersaving mode, or the normal access mode), and/or mode switching, forexample, to align the base station 2802 and the wireless device 2804regarding a mode of the wireless device 2804. The wireless device 2804may transmit one or more indicators to the base station 2802 indicatingif a mode (e.g., the power saving mode, or the normal access mode) issupported, and/or if mode switching is supported by the wireless device2804. The one or more indicators may indicate, for example, at least oneof: if the wireless device 2804 supports a power saving mode in an RRCidle state, if the wireless device 2804 supports a power saving mode inan RRC inactive state, and/or if the wireless device 2804 supports apower saving mode in an RRC connected state. The one or more indicatorsmay indicate that a power saving mode is triggered (e.g., activatedand/or enabled). The one or more indicators may comprise at least oneof: an indicator of a power saving operation configuration of aplurality of power saving operation configurations that is triggered (oractivated/enabled), and one or more parameters (e.g., QoS, and/ortraffic type) of a service of the wireless device 2804. The one or moreindicators may be contained in an RRC message, a MAC CE, and/or DCI. Theone or more indicators may be contained, for example, in a wirelessdevice-capability message (e.g., UE-NR-Capability IE, orUE-MRDC-Capability IE, and/or Phy-Parameters IE).

The base station 2802 may send (e.g., transmit), to the wireless device2804, an activation/deactivation command indicating anactivation/deactivation of a power saving operation configuration of theat least one power saving operation configuration. Theactivation/deactivation command may be contained in a MAC CE that isindicated (e.g., identified) by a MAC subheader with an LCID value. TheLCID value may be different from an LCID value listed in FIG. 18A firstMAC CE for activation/deactivation of a power saving operationconfiguration may be different, for example, from a second MAC CE for aDRX operation. A first LCID value of the first MAC CE may be differentfrom a second LCID value (e.g., “111011” or “111100” as listed in FIG.18 ) of the second MAC CE. The MAC CE for activation/deactivation of apower saving operation configuration may comprise, for example, at leastone of: a power saving configuration identifier (e.g., an index, anindicator, or an ID) indicating the power saving operationconfiguration, of the at least one power saving operationconfigurations, that may be activated/deactivated; a cell ID indicatingan identity of a cell for which the power saving operation configurationmay apply; and/or a BWP ID indicating a downlink BWP for which the powersaving operation configuration may apply. A MAC CE foractivation/deactivation of the power saving operation configuration mayhave, for example, a size of zero bits, one bit, two bits, or any otherquantity of bits. The MAC CE for activation/deactivation of the powersaving operation configuration may have a fixed size of zero bit, forexample, if the one or more RRC messages comprise configurationparameters of at most one power saving operation configuration.

The activation/deactivation command may be contained in DCI transmittedwith a DCI format. The DCI may comprise at least one of: a power savingconfiguration identifier indicating the power saving operationconfiguration of the at least one power saving operation configurationthat may be activated/deactivated, a cell ID indicating an identity of acell for which the power saving operation configuration may apply,and/or a BWP ID indicating a downlink BWP for which the power savingoperation configuration may apply.

At time t₂, the wireless device 2804 may receive theactivation/deactivation command indicating the activation of the powersaving operation configuration of the at least one power savingoperation configuration. The wireless device 2804 may switch from thenormal access mode to a power saving mode by applying parameters of thepower saving operation configuration of the at least one power savingoperation configuration. The power saving operation configuration may beindicated by a power saving configuration index in theactivation/deactivation command. The wireless device 2804 may monitor apower saving signal/channel corresponding to the power saving operationconfiguration, based on receiving the activation/deactivation command.The wireless device 2804 may monitor at most one power savingsignal/channel for the power saving operation, for example, if at mostone power saving operation configuration is comprised in the one or moreRRC messages.

The wireless device 2804 may monitor the power saving signal/channel ina time window with a periodicity associated with the power savingoperation configuration of the at least one power saving operationconfiguration. The wireless device 2804 may monitor the power savingsignal/channel in a frequency resource associated with the power savingoperation configuration of the at least one power saving operationconfiguration. The wireless device 2804 may monitor, the power savingchannel, in a control resource set and/or a search space associated withthe power saving operation configuration of the at least one powersaving operation configuration. The wireless device 2804 may monitor thepower saving signal/channel on a BWP of a cell, wherein the BWP and/orthe cell may be indicated in the activation/deactivation command and/orthe power saving operation configuration of the at least one powersaving operation configuration.

The wireless device 2804 may receive a power saving signal (e.g., via apower saving channel). The wireless device 2804 may receive the powersaving signal based on the monitoring of the channel (e.g., in a timewindow associated with the power saving operation configuration, in afrequency resource associated with the power saving operationconfiguration, and/or in a control resource set and/or a search spaceassociated with the power saving operation configuration, etc.). Thewireless device 2804 may monitor PDCCHs based on (e.g., after or inresponse to) receiving the power saving signal. The wireless device 2804may monitor PDCCHs continuously based on receiving the power savingsignal, for example, if a DRX operation is not configured. The wirelessdevice 2804 may monitor PDCCHs discontinuously based on receiving thepower saving signal, for example, if the DRX operation is configured.The wireless device 2804 may transmit data packets to and/or receivedata packets from the base station 2802, for example, if the wirelessdevice 2804 receives, via the PDCCHs, DCI indicating an uplink grant,and/or DCI indicating a downlink assignment. The wireless device 2804may not monitor (e.g., refrain from monitoring) PDCCHs, for example, ifthe wireless device 2804 fails to receive the power saving signal,regardless of whether the DRX operation is configured or not.

The base station 2802 may trigger the wireless device 2804 to switchfrom the power saving mode to the normal access mode. The base station2802 may trigger the wireless device 2804 to switch, for example, if adata service (e.g., not suitable for the power saving mode) is launched.The base station 2802 may send (e.g., transmit), to the wireless device2804, an activation/deactivation command indicating a deactivation ofthe power saving operation configuration. At t₃, the wireless device2804 may receive the activation/deactivation command indicating thedeactivation of the power saving operation configuration. The wirelessdevice 2804 may switch from the power saving mode to the normal accessmode, for example, based on receiving the activation/deactivationcommand for deactivation of the power saving operation. The wirelessdevice 2804 may stop monitoring the power saving signal/channel, forexample, based on receiving the activation/deactivation command fordeactivation of the power saving operation. The wireless device 2804 may(e.g., based on switching to the normal access mode) monitor PDCCHscontinuously if a DRX operation is not configured, and/or monitor thePDCCHs discontinuously if a DRX operation is configured.

A base station and/or a wireless device may switch to a power savingmode, for example, based on a determination (e.g., at the base stationand/or the wireless device) that an on-going data service is suitablefor a power saving operation. The base station and/or the wirelessdevice may switch to a normal access mode, for example, based on adetermination (e.g., at the base station and/or the wireless device)that an on-going data service is not suitable for a power savingoperation. The wireless device and/or the base station may switchbetween the power saving mode and the normal access mode, for example,based on one or more operations described herein.

FIG. 29 shows an example of a command-based activation and a timer-baseddeactivation of a power saving operation. A base station 2902 may send(e.g., transmit), to a wireless device 2904, one or more RRC messages.The wireless device 2904 may receive the one or more RRC messages at orafter time t₁. The one or more RRC messages may comprise parameters ofone or more power saving operation configurations. A power savingoperation configuration may be indicated (e.g., identified) by a powersaving operation configuration index. Parameters of a power savingoperation configuration may comprise, for example, at least one of: asignal format of a power saving signal, a time window in which a powersaving signal may be transmitted, power saving signal sequencegeneration parameters, a value of a periodicity of the transmission ofthe power saving signal, a time resource/frequency resource on which thepower saving signal may be transmitted, parameters of a control resourceset (e.g., time and/or frequency resource of the power saving channel),a DCI format, and/or a BWP of a cell on which the wireless device 2904may monitor the power saving signal/channel. The parameters of the powersaving operation configuration may comprise a power saving timer valueof a power saving timer. The power saving timer value may indicate aduration for which the power saving operation may apply. The one or moreRRC messages may further comprise one or more parameters described withreference to FIG. 28 .

The base station 2902 may transmit, to the wireless device 2904, anactivation/deactivation command indicating an activation of a powersaving operation configuration of the one or more power saving operationconfigurations. The wireless device 2904 may receive theactivation/deactivation command at time t₂. The activation/deactivationcommand may be in a MAC CE or DCI. The wireless device 2904 may switchfrom a normal access mode to a power saving mode, based on receiving theactivation/deactivation command indicating an activation of the powersaving operation configuration. The wireless device 2904 may switch fromthe normal access mode to the power saving mode, based on (e.g., after)a configured/predefined switch gap following the reception of theactivation/deactivation command. The wireless device 2904 may monitor apower saving signal/channel based on the power saving operationconfiguration. The wireless device 2904 may start a power saving timerbased on the power saving timer value (e.g., after or in response toreceiving the activation/deactivation command indicating the activationof the power saving operation configuration).

The wireless device 2904 may receive a power saving signal (e.g., via apower saving channel). The wireless device 2904 may receive the powersaving signal, for example, based on the monitoring of the power savingsignal/channel (e.g., based on a periodicity indicated in the powersaving operation configuration, in a time window associated with thepower saving operation configuration, in a frequency resource associatedwith the power saving operation configuration, and/or in a controlresource set and/or a search space associated with the power savingoperation configuration, etc.). The wireless device 2904 may monitorPDCCHs based on receiving the power saving signal. The wireless device2904 may monitor PDCCHs continuously, for example, if a DRX operation isnot configured. The wireless device 2904 may monitor the PDCCHsdiscontinuously, for example, if the DRX operation is configured. Thewireless device may fail to receive the power saving signal based on themonitoring of the power saving signal/channel. The wireless device 2904may not monitor (e.g., refrain from monitoring) the PDCCHs, for example,if the wireless device 2904 fails to receive the power saving signal.The wireless device 2904 may not monitor (e.g., refrain from monitoring)the PDCCHs regardless of whether a DRX operation is configured or not.The wireless device 2904 may repeat monitoring the power savingsignal/channel with a periodicity indicated in the power savingoperation configuration, for example, if the power saving timer isrunning and has not expired.

At time t₃, the power saving timer may expire. The wireless device 2904may switch from the power saving mode to the normal access mode, forexample, based on the expiration of the power saving timer. The wirelessdevice may stop monitoring the power saving signal/channel, for example,based on the expiration of the power saving timer. The wireless devicemay (e.g., based on switching to the normal access mode) monitor PDCCHscontinuously if a DRX operation is not configured, or monitor the PDCCHsdiscontinuously if the DRX operation is configured. The base station2902 may need not send an activation/deactivation command indicating adeactivation of the power saving operation configuration to facilitate aswitch, at the wireless device 2904, from the power saving mode to thenormal mode. This may result in improved spectrum efficiency within acommunication network.

A wireless device (e.g., the wireless device 2804 or the wireless device2904) may monitor PDCCHs discontinuously, by applying parameters of oneof one or more DRX cycles. The parameters of a DRX cycle may comprise avalue of a DRX On duration and a value of a duration of the DRX cycle.The one or more DRX cycles may comprise at least a first DRX cycle and asecond DRX cycle. A first duration of the first DRX cycle may be shorterthan a second duration of the second DRX cycle. A first DRX On durationof the first DRX cycle may be shorter than a second DRX On duration ofthe second DRX cycle. The wireless device may monitor the PDCCHsdiscontinuously by applying parameters of the first DRX cycle of the oneor more DRX cycles, for example, based on an expiration of the powersaving timer. The wireless device may monitor the PDCCHs discontinuouslyby applying parameters of the second DRX cycle of the one or more DRXcycles, for example, based on an expiration of the power saving timer.

A wireless device may receive an activation/deactivation commandindicating an activation of the power saving operation configuration,for example, at a time in which the wireless device is transmitting oneor more uplink transmissions. The one or more uplink transmissions maycomprise, for example, at least one of: a preamble transmission of arandom access procedure (e.g., uplink synchronization, or beam failurerecovery), SRS transmission, and/or PUSCH/PUCCH transmission. Thewireless device may abort (or stop, or refrain from transmitting) theone or more uplink transmissions and may apply the power savingoperation configuration, for example, based on receiving the activationcommand/deactivation command indicating an activation of the of thepower saving operation configuration. This may result in an interruptionin the one or more uplink transmissions and/or any procedures associatedwith the uplink transmissions (e.g., an uplink synchronizationprocedure, a beam failure recovery procedure, etc.).

A wireless device may ignore an activation/deactivation commandindicating an activation of a power saving operation, for example, ifthe wireless device receives the activation/deactivation command at atime in which an uplink transmission (e.g., corresponding to a RAprocedure, a beam failure recovery procedure, and/or an SRStransmission) is ongoing (e.g., on an PCell). The wireless device maysuccessfully finish the uplink transmission by ignoring theactivation/deactivation command. The wireless device may ignore theactivation/deactivation command by not applying the power savingoperation configuration and/or may continue performing one or moreuplink transmissions, for example, based on receiving the activationcommand/deactivation command indicating an activation of the of thepower saving operation configuration. The wireless device may performthe one or more uplink transmissions, for example, after or in responseto receiving a power saving signal.

A wireless device may continue a beam failure recovery procedure (e.g.,continue an uplink transmission corresponding to a beam failure recoveryprocedure) on a PCell, for example, if the wireless device receives anactivation/deactivation command at a time in which the beam failurerecovery procedure is ongoing. A wireless device may stop a beam failurerecovery procedure (e.g., stop/abort an uplink transmissioncorresponding to a beam failure recovery procedure) on an SCell, forexample, if the wireless device receives an activation/deactivationcommand at a time in which the beam failure recovery procedure isongoing. By ignoring an activation/deactivation command (e.g.,continuing a beam failure recovery procedure) (e.g., on a PCell), awireless device may increase the likelihood of a successful procedure(e.g., beam failure recovery procedure) occurring with reduced latency,such as by avoiding interruption(s) of one or more uplink transmissionsand/or procedures associated with the uplink transmissions (e.g., anuplink synchronization procedure, a beam failure recovery procedure,etc.). By stopping a beam failure recovery procedure, based on or inresponse to an activation/deactivation command (e.g., on an SCell), awireless device may reduce signaling overhead such as avoidingtransmissions in a beam failure recovery procedure that may beunsuccessful.

FIG. 30 shows an example of a command-based activation and a timer-baseddeactivation of a power saving operation. A base station 3002 may send(e.g., transmit) to a wireless device 3004, one or more configurationmessages (e.g., RRC messages). The wireless device 3004 may receive theone or more RRC messages at or after time t₁. The one or more RRCmessages may comprise parameters of one or more power saving operationconfigurations. The one or more RRC messages may comprise a power savingtimer value of a power saving timer. The one or more power savingoperation configurations may comprise, for example, corresponding valuesof a power saving timer. The one or more RRC messages may furthercomprise one or more parameters described with reference to FIGS. 28 and29 .

The base station 3002 may transmit, to the wireless device 3004, anactivation/deactivation command indicating an activation of a powersaving operation configuration. The activation/deactivation command maybe in a MAC CE and/or DCI. At time t₂, the wireless device 3004 mayreceive the activation/deactivation command indicating an activation ofthe power saving operation configuration. The wireless device 3004 mayswitch from a normal access mode to a power saving mode, for example,based on receiving the activation/deactivation command indicating anactivation of the power saving operation configuration. The wirelessdevice 3004 may monitor a power saving signal/channel based on the powersaving operation configuration (e.g., after or in response to receivingthe activation/deactivation command indicating the activation of thepower saving operation configuration). The wireless device 3004 maystart the power saving timer based on the power saving timer value(e.g., after or in response to receiving the activation/deactivationcommand indicating the activation of the power saving operationconfiguration).

At time t₃, the wireless device 3004 may receive the power saving signal(e.g., via the power saving channel). The wireless device 3004 mayreceive the power saving signal, for example, based on the monitoring ofthe power saving signal (e.g., based on a periodicity indicated in thepower saving operation configuration, in a time window associated withthe power saving operation configuration, in a frequency resourceassociated with the power saving operation configuration, and/or in acontrol resource set and/or a search space associated with the powersaving operation configuration, etc.). The wireless device 3004 may(re-)start the power saving timer, for example, based on (e.g., after orin response to) receiving the power saving signal. The (re-)starting thepower saving timer may comprise resetting the value of the power savingtimer to the power saving timer value (as received in the one or moreRRC messages) and/or restarting the power saving timer with the powersaving timer value.

The wireless device 3004 may monitor PDCCHs based on (e.g., after or inresponse to) receiving a power saving signal. The wireless device 3004may monitor the PDCCHs continuously, for example, if a DRX operation isnot configured. The wireless device 3004 may monitor the PDCCHsdiscontinuously, for example, if the DRX operation is configured. Thewireless device 3004 may fail to receive the power saving signal basedon the monitoring the power saving signal/channel. The wireless device3004 may not monitor (e.g., refrain from monitoring) the PDCCHs,regardless of whether a DRX operation is configured or not, for example,if the wireless device 3004 fails to receive the power saving signal.The wireless device 3004 may repeat monitoring the power savingsignal/channel with a periodicity indicated in the power savingoperation configuration, for example if the power saving timer isrunning and/or has not expired.

FIG. 31 shows an example of activation/deactivation of a power savingoperation. FIG. 31 further shows management of timer(s) in a powersaving operation. A base station 3102 may send (e.g., transmit), to awireless device 3104, one or more configuration messages (e.g., RRCmessages). The wireless device 3104 may receive the one or more RRCmessages at or after time t₁. The one or more RRC messages may compriserespective configuration parameters corresponding to a plurality ofcells. Configuration parameters of a cell, in the plurality of cells,may comprise, for example, at least one of: one or more BWPs, a BWPinactivity timer value of a BWP inactivity timer, a cell deactivationtimer value of a cell deactivation timer, a power saving timer value ofa power saving timer, and/or configuration parameters of a power savingoperation configuration. The one or more RRC messages may furthercomprise one or more parameters described with references FIGS. 28-30 .

At or after time t₂, the wireless device may receive one or more RRCmessages, MAC CE(s), and/or DCI. The wireless device 3104 may activate acell of the plurality of cells, for example, based on receiving an RRCmessage that indicates an activation of the cell, and/or MAC CE(s) thatindicates an activation of the cell. The wireless device 3104 mayactivate a BWP of the one or more BWPs, for example, based on receivingan RRC message that indicates an activation of the BWP, and/or DCI thatindicates an activation of the BWP. The wireless device 3104 may (e.g.,based on activation of the BWP, and/or activation of the cell): start aBWP inactivity timer based on a BWP inactivity timer value correspondingto the cell, start a cell deactivation timer based on a celldeactivation timer value corresponding to the cell, and/or monitorPDCCHs as required. The wireless device 3104 may restart the BWPinactivity timer and/or the cell deactivation timer based on receivingDCI (e.g., in the PDCCHs) indicating a downlink assignment or an uplinkgrant.

At t₃, the wireless device 3104 may receive, from the base station 3102,an activation (or enabling) command indicating an activation of thepower saving operation configuration. The wireless device 3104 mayactivate the power saving operation configuration based on receiving theactivation command. The activation (or enabling) command may be in a MACCE and/or DCI. The wireless device 3104 may (e.g., based on receivingthe activation command for the power saving operation configuration):monitor a power saving signal/channel based on the power savingoperation configuration, start the power saving timer based on the powersaving timer value, stop the BWP inactivity timer, and/or stop the celldeactivation timer. Stopping the BWP inactivity timer and/or the celldeactivation timer (e.g., based on the activation of a power savingoperation configuration) may avoid misalignment of a state of a BWP,and/or a cell, between the base station 3102 and the wireless device3104.

At time t₄, the wireless device 3104 may receive the power saving signal(e.g., via the power saving channel) based on the monitoring the powersaving signal/channel. The wireless device 3104 may (re-)start the powersaving timer, for example, based on receiving the power saving signal.The wireless device 3104 may (e.g., based on receiving the power savingsignal): (re-) start the BWP inactivity timer, and/or (re-)start thecell deactivation timer. The (re-)starting the BWP inactivity timer maycomprise resetting the value of the BWP inactivity timer to the BWPinactivity timer value and restarting the BWP inactivity timer with theBWP inactivity timer value. The (re-)starting the cell deactivationtimer may comprise resetting the value of the cell deactivation timer tothe cell deactivation timer value and/or restarting the celldeactivation timer with the cell deactivation timer value.

The wireless 3104 device may monitor PDCCHs based on receiving the powersaving signal. The wireless device 3104 may monitor the PDCCHscontinuously, for example, if a DRX operation is not configured. Thewireless device 3104 may monitor the PDCCH discontinuously, for example,if the DRX operation is configured. The wireless device 3104 may fail toreceive the power saving signal based on the monitoring the power savingsignal/channel. The wireless device 3104 may not monitor (e.g., refrainfrom monitoring) the PDCCHs, for example, if the wireless device 3104fails to receive the power saving signal. The wireless device 3104 maynot monitor (e.g., refrain from monitoring) the PDCCHs regardless ofwhether a DRX operation is configured or not. The wireless device 3104may repeat monitoring the power saving signal/channel with a periodicityindicated in the power saving operation configuration, for example, ifthe power saving timer is running and has not expired.

The wireless device 3104 may deactivate the power saving operation basedon an expiration of the power saving timer. The wireless device 3104 mayswitch from the power saving operation to a normal access mode, forexample, based on the expiration of the power saving timer. The wirelessdevice 3104 may (e.g., based on the expiration of the power savingtimer): stop the power saving timer, (re-)start the BWP inactivity timer(re-)start the cell deactivation timer, and/or monitor PDCCHs asrequired.

FIG. 32 shows an example of an activation/deactivation-based powersaving operation. At time t₁, a wireless device 3204 may receive anactivation command of a power saving operation configuration. Parametersof the power saving operation configuration may comprise at least oneof: a length of a wake-up window, time/frequency radio resources of atransmission of a power saving signal (e.g., in the wakeup window), aperiodicity of the wake-up window, a power saving time duration 3208 forapplying the power saving operation configuration, etc. The wirelessdevice 3204 may perform a power saving operation, for example, based onreceiving the activation command of the power saving operationconfiguration. The wireless device 3204 may perform a power savingoperation, for example, based on the parameters of power savingoperation configuration. The wireless device 3204 may perform the powersaving operation in the power saving time duration 3208 (e.g., asindicated by the parameters of the power saving operationconfiguration). The wireless device 3204 may (e.g., in the power savingtime duration 3208): monitor the power saving signal/channel in thetime/frequency radio resources of the wake-up window (e.g., a wake-upwindow 3206), monitor PDCCHs based on (e.g., after or in response to)receiving the power saving signal, and/or skip monitoring (e.g., refrainfrom monitoring) the PDCCHs based on not receiving the power savingsignal. The wireless device 3204 may monitor the power savingsignal/channel with the periodicity indicated by the parameters of thepower saving operation configuration

The wireless device 3204 may monitor the PDCCHs, in the power savingtime duration 3208, based on receiving a power saving signal in thewakeup window 3206. The wireless device 3204 may monitor the PDCCHscontinuously, for example, if a DRX operation is not configured. Thewireless device may monitor the PDCCHs discontinuously, for example, ifthe DRX operation is configured. The wireless device 3204 may skipmonitoring (e.g., refrain from monitoring) the PDCCHs, in the powersaving time duration 3208, for example, if the wireless device 3204fails to receive the power saving signal. The wireless device 3204 mayskip monitoring the PDCCHs regardless of whether a DRX operation isconfigured or not. The wireless device 3204 may repeat (e.g., in thepower saving time duration 3208): monitoring the power savingsignal/channel in the time/frequency radio resources of a wake-upwindow, monitoring PDCCHs based on (e.g., after or in response to)receiving the power saving signal, and/or skipping monitoring the PDCCHsbased on not receiving the power saving signal.

At time t₂, the wireless device 3204 may receive a deactivation commandof the power saving operation configuration. At time t₂, a power savingtimer may expire. The wireless device 3204 may deactivate the powersaving operation configuration based on (e.g., after or in response to)receiving the deactivation command, and/or an expiration of the powersaving timer. The wireless device 3204 may (e.g., based on deactivatingthe power saving operation configuration): stop monitoring the powersaving signal/channel, and/or start monitoring the PDCCHs. The wirelessdevice 3204 may monitor the PDCCHs continuously, for example, if a DRXoperation is not configured. The wireless device may monitor the PDCCHsdiscontinuously, for example, if the DRX operation is configured.

FIG. 33 shows an example method of a power saving operation. At step3302, a wireless device may receive one or more RRC messages. The one ormore RRC messages may comprise parameters of a plurality of power savingoperation configurations. The one or more RRC messages may also comprisesecond parameters of a DRX operation, for example, if the wirelessdevice is to be configured for the DRX operation. At step 3304, thewireless device may receive a first command indicating an activation ofa power saving operation configuration of the plurality of power savingoperation configurations. At step 3306, the wireless device may monitora power saving signal/channel, for example, based on parameters of thepower saving operation configuration and based on a reception of thefirst command. The wireless device may receive a power saving signal,for example, based on the monitoring of the power saving signal/channel.At step 3308, the wireless device may start monitoring PDCCH based on areception of the power saving signal. The wireless device may startmonitoring PDCCH discontinuously based on the second parameter of theDRX operation, for example, if the DRX operation is configured. Thewireless device may start monitoring PDCCH continuously, for example, ifthe DRX operation is not configured. The wireless device may fail toreceive the power saving signal, for example, based on the monitoring ofthe power saving signal/channel. The wireless device may not monitor(e.g., refrain from monitoring) the PDCCHs, regardless of whether theDRX operation is configured or not, for example, if the wireless devicefails to receive the power saving signal. The wireless device may repeatone or more of the steps 3306 and 3308. At step 3310, the wirelessdevice may receive a second command that indicates a deactivation of thepower saving operation configuration. At step 3312, the wireless devicemay stop monitoring (e.g., refrain from monitoring) the power savingsignal/channel, for example, based on receiving the second command. Thewireless device may monitor the PDCCHs based on receiving the secondcommand. The wireless device may monitor the PDCCHs discontinuously, forexample, if the DRX operation is configured. The wireless device maymonitor the PDCCHs continuously, for example, if the DRX operation isnot configured. The wireless device may transmit to and/or receive froma base station, one or more data packets, for example, based onreceiving DCI (e.g., one or more DCI messages) in the PDCCHs (e.g., atstep 3308 and/or step 3312). The DCI may indicate a downlink assignmentor an uplink grant.

FIG. 34 shows an example method of a power saving operation. At step3402, a wireless device may receive one or more RRC messages. The one ormore RRC messages may comprise parameters of a plurality of power savingoperation configurations. The one or more RRC messages may furthercomprise a power saving timer value of a power saving timer. At step3404, the wireless device may receive a command indicating an activationof a power saving operation configuration of the plurality of powersaving operation configurations. At step 3606, the wireless device maymonitor a power saving signal/channel, for example, based on a receptionof the command and/or based on parameters of the power saving operationconfiguration. The wireless device may start the power saving timerbased on the reception of the command. At step 3408, the wireless devicemay receive the power saving signal. At step 3410, the wireless devicemay (re-)start the power saving timer, for example, based on a receptionof the power saving signal. The wireless device may start monitoringPDCCHs, for example, continuously if a DRX is not configured, ordiscontinuously if the DRX operation is configured. The wireless devicemay fail to receive the power saving signal. The wireless device may notmonitor (e.g., refrain from monitoring) the PDCCHs, regardless ofwhether the DRX operation is configured or not, for example, if thewireless device fails to receive the power saving signal. The wirelessdevice may repeat one or more of the steps 3406, 3408 and 3410. Thepower saving timer may expire. At step 3412, the wireless device maystop monitoring (e.g., refrain from monitoring) the power savingsignal/channel, for example, based on an expiration of the power savingtimer. The wireless device may start monitoring the PDCCHs, for example,based on the expiration of the power saving timer. The wireless devicemay monitor the PDCCHs, for example, continuously if a DRX is notconfigured, or discontinuously if the DRX operation is configured. Thewireless device may transmit to and/or receive from the base station,one or more data packets based on receiving DCI (e.g., one or more DCImessages) in the PDCCHs (e.g., at step 3410 and/or step 3412). The DCImay indicate a downlink assignment or an uplink grant.

A wireless device may monitor a downlink control channel based on thewireless device being in a first state. The wireless device may receive(e.g., during the monitoring) a first MAC CE that indicates a transitionfrom the first state to a second state. The first MAC CE may comprise,for example, one or more first fields that indicate a cell and/or abandwidth part, and/or a second field that indicatesactivation/deactivation of the second state. The wireless device maytransition from the first state into the second state, for example,based on the first MAC CE. The wireless device may stop monitoring thedownlink control channel, for example, based on transitioning from thefirst state to the second state. The wireless device may monitor adownlink radio resource for receiving a wake-up signal, for example,based on transitioning from the first state to the second state. Thewireless device may receive the wake-up signal, for example, in thedownlink radio resource. The wireless device may transition from thesecond state into the first state, for example, based on receiving thewake-up signal. The wireless device may receive DCI, for example, if thewireless device is in the first state. The wireless device may receivedata packets based on receiving the DCI. The wireless device may fail toreceive the wake-up signal. The wireless device may stay in the secondstate, for example, if the wireless device does fails to receive thewake-up signal. The wireless device may repeat monitoring the at leastdownlink radio resource, for detecting one or more wake-up signals.

A wireless device may receive a MAC PDU comprising a MAC CE and a MACsubheader. The MAC CE may indicate a transition to a power saving state.The MAC subheader may comprise an LCID value that corresponds to anactivation/deactivation command of a power saving operationconfiguration. The wireless device may transition to the power savingstate, for example, based on receiving the MAC PDU. The wireless devicemay monitor a downlink radio resource, for example, based ontransitioning to the power saving state. The wireless device may receivea wake-up signal in the downlink radio resource.

A wireless device may receive one or more messages that compriseconfiguration parameters of a wake-up signal corresponding to a cell.The configuration parameters may comprise, for example, a first timervalue of a wake-up timer and a second timer value of a go-to-sleeptimer. The wireless device may (e.g., based on the wireless devicetransitioning to a first state): start the wake-up timer based on thefirst timer value, start the go-to-sleep timer based on the second timervalue, and/or monitor the wake-up signal. The wireless device may(re-)start the wake-up timer and/or the go-to-sleep timer, for example,based on receiving the wake-up signal. The wireless device may (e.g.,based on an expiration of the wake-up timer): transition from the firstmode to a second mode, and/or monitor a PDCCH of the cell. The wirelessdevice may (e.g., based on an expiration of the go-to-sleep timer):transition from the first state to a third state, and/or skip monitoringthe PDCCH of the cell.

A wireless device may perform a method comprising multiple operations.The wireless device may receive one or more first messages comprisinginformation (e.g., configuration parameters) associated with a pluralityof power saving configurations of a cell of a plurality of cells. Thewireless device may receive a second message comprising: a first fieldthat indicates a first power saving configuration of the plurality ofpower saving configurations, and a second field that indicates the cell.The wireless device may monitor, based on the first power savingconfiguration, a power saving channel. The wireless device may receive,via the power saving channel, a wake-up indication. The wireless devicemay monitor, based on the receiving the wake-up indication, a downlinkcontrol channel of the cell.

The wireless device may also perform one or more additional operationsor include additional elements in conjunction with the described method.The second message may further comprise a third field that indicates abandwidth part of the cell. The monitoring the power saving channel maycomprise monitoring the power saving channel on the bandwidth part ofthe cell. The one or more first messages may comprise configurationparameters of the first power saving configuration. The configurationparameters of the first power saving configuration comprise at least oneof a periodicity of the power saving channel, a duration of the powersaving channel, a number of resource blocks in a frequency domain, abandwidth part indicator indicating a bandwidth of the cell, a searchspace set, or a control resource set. The monitoring the power savingchannel may be based on at least one of the configuration parameters ofthe first power saving configuration. The wireless device may determine,based on receiving a third message, that a beam failure recoveryprocedure is ongoing on the cell. The wireless device may, based on thedetermining that a beam failure recovery procedure is ongoing on thecell: continue the beam failure recovery procedure, and delayingadjusting the cell into a power saving state. The wireless device mayreceive, via the monitored downlink control channel, a downlinkassignment. The wireless device may receive, via the downlinkassignment, downlink transport blocks. The wireless device may receive,via the monitored downlink control channel, an uplink grant. Thewireless device may transmit, based on the uplink grant, uplinktransport blocks. The second message may comprise at least one of: amedium access control (MAC) control element (CE), or downlink controlinformation (DCI). The wireless device may receive a third message. Thethird message may indicate a second power saving configuration of theplurality of power saving configurations. The second power savingconfiguration may comprise at least one configuration parameter that isdifferent from a corresponding configuration parameter of the firstpower saving configuration. The wireless device may stop a secondarycell deactivation timer of the cell based on receiving the secondmessage. The wireless device may stop a bandwidth part inactivity timerof an active bandwidth part of the cell based on receiving the secondmessage. The monitoring the downlink control channel may comprisediscontinuously monitoring the downlink control channel based on adiscontinuous reception (DRX) configuration. The discontinuouslymonitoring the downlink control channel may comprise at least one of:monitoring the downlink control channel in a DRX active time of the DRXconfiguration, and skipping monitoring the downlink control channel in aDRX inactive time of the DRX configuration. The wireless device maystart a power saving timer based on receiving the second message. Thewireless device may, based on an expiration of the power saving timer,stop the monitoring of the power saving channel. The method of any oneof claims 1 to 13, wherein the cell comprises a primary cell. Thewireless device may activate the cell and starting a secondary celldeactivation timer of the cell. The wireless device may skip monitoringthe downlink control channel based on not receiving the wake-upindication. The one or more first messages may further compriseconfiguration parameters of the downlink control channel. Theconfiguration parameters of the downlink control channel may comprise atleast one of: a periodicity of the downlink control channel, a durationof the downlink control channel, a number of resource blocks infrequency domain, at least a search space set, or at least a controlresource set. Monitoring the downlink control channel may comprisecontinuously monitoring the downlink control channel if a discontinuousreception (DRX) operation is not configured. Continuously monitoring thedownlink control channel may comprise monitoring the downlink controlchannel in one or more downlink control channel monitoring occasionsconfigured by a base station. The wake-up indication may indicatemonitoring the downlink control channel of the cell. The wake-upindication may further indicate at least one of: transmitting on uplinkcontrol channel of the cell, transmitting on uplink shared channel ofthe cell, or receiving on a downlink shared channel of the cell. Thewireless device may receive a third message comprising: the first fieldthat indicates a second power state configuration of the plurality ofpower saving configurations, and the second field that indicates thecell. The wireless device may stop a secondary cell deactivation timerof the cell based on receiving the third message. The wireless devicemay stop a bandwidth part inactivity timer of an active bandwidth partof the cell based on receiving the third message.

Systems, devices and media may be configured with the method. Acomputing device may comprise one or more processors; and memory storinginstructions that, when executed, cause the computing device to performthe described method, additional operations and/or include theadditional elements. A system may comprise a first computing deviceconfigured to perform the described method, additional operations and/orinclude the additional elements; and a second computing deviceconfigured to send the one or more first messages. A computer-readablemedium may store instructions that, when executed, cause performance ofthe described method, additional operations and/or include theadditional elements.

A wireless device may perform a method comprising multiple operations.The wireless device may receive one or more first messages comprisinginformation (e.g., configuration parameters) associated with a pluralityof power saving configurations. The wireless device may monitor, basedon a first field that indicates a first power saving configuration ofthe plurality of power saving configurations, a power saving channel.The wireless device may receive, via the power saving channel, a wake-upindication of a cell. The wireless device may, based on receiving thewake-up indication, monitor, for a downlink assignment or an uplinkgrant, a downlink control channel of the cell.

The wireless device may also perform one or more additional operationsor include additional elements in conjunction with the described method.The wireless device may receive a second message. The second message maycomprise the first field that indicates the first power savingconfiguration of the plurality of power saving configurations, and asecond field that indicates the cell. The second message may comprise atleast one of a medium access control (MAC) control element (CE), ordownlink control information (DCI). The one or more first messages maycomprise information (e.g., configuration parameters) associated withthe first power saving configuration. The information associated withthe first power saving configuration comprise at least one of: aperiodicity of the power saving channel, a duration of the power savingchannel, a number of resource blocks in a frequency domain, a bandwidthpart indicator indicating a bandwidth of the cell, a search space set,or a control resource set. The monitoring the power saving channel maybe based on at least one of the information associated with the firstpower saving configuration. The wireless device may determine, based onreceiving a third message, that a beam failure recovery procedure isongoing on the cell. The wireless device may, based on the determiningthat a beam failure recovery procedure is ongoing on the cell continuethe beam failure recovery procedure, and delay adjusting the cell into apower saving state. The wireless device may receive the downlinkassignment. The wireless device may receive, based on the downlinkassignment, downlink transport blocks. The wireless device may receivethe uplink grant. The wireless device may transmit, based on the uplinkgrant, uplink transport blocks.

Systems, devices and media may be configured with the method. Acomputing device may comprise one or more processors; and memory storinginstructions that, when executed, cause the computing device to performthe described method, additional operations and/or include theadditional elements. A system may comprise a first computing deviceconfigured to perform the described method, additional operations and/orinclude the additional elements; and a second computing deviceconfigured to send the one or more first messages. A computer-readablemedium may store instructions that, when executed, cause performance ofthe described method, additional operations and/or include theadditional elements.

A wireless device may perform a method comprising multiple operations.The wireless device may receive one or more first messages comprisinginformation (e.g., configuration parameters) associated with a beamfailure recovery procedure of a cell, and information (e.g.,configuration parameters) associated with a plurality of power savingconfigurations of the cell. The wireless device may receive a secondmessage. The second message may indicates adjusting the cell into apower saving state, and a first power saving configuration of theplurality of power saving configurations. The wireless device maydetermine, based on receiving the second message, that a beam failurerecovery procedure is ongoing on the cell. The wireless device may,based on the determining that the beam failure recovery procedure isongoing on the cell: continue the beam failure recovery procedure, anddelay adjusting the cell into the power saving state.

The wireless device may also perform one or more additional operationsor include additional elements in conjunction with the described method.The wireless device may, based on determining that the beam failurerecovery procedure is not ongoing on the cell: adjusting the cell intothe power saving state; monitor, based on the first power savingconfiguration, a power saving channel; receive, via the power savingchannel, a wake-up indication of the cell; and monitor, based on thereceiving the wake-up indication, a downlink control channel of thecell. The one or more first messages may comprise information (e.g.,configuration parameters) associated with the first power savingconfiguration. The information associated with the first power savingconfiguration may comprise at least one of: a periodicity of the powersaving channel, a duration of the power saving channel, a number ofresource blocks in a frequency domain, a bandwidth part indicatorindicating a bandwidth of the cell, a search space set, or a controlresource set. The monitoring the power saving channel may be based on atleast one of the information associated with the first power savingconfiguration. The wireless device may receive a third message. Thethird message may indicate a second power saving configuration of theplurality of power saving configurations. The second power savingconfiguration may comprise at least one configuration parameter that isdifferent from a corresponding configuration parameter of the firstpower saving configuration. The wireless device may, based on receivingthe second message, at least one of: stop a secondary cell deactivationtimer of the cell, or stop a bandwidth part inactivity timer of anactive bandwidth part of the cell. The second message may comprise atleast one of a medium access control (MAC) control element (CE), ordownlink control information (DCI).

Systems, devices and media may be configured with the method. Acomputing device may comprise one or more processors; and memory storinginstructions that, when executed, cause the computing device to performthe described method, additional operations and/or include theadditional elements. A system may comprise a first computing deviceconfigured to perform the described method, additional operations and/orinclude the additional elements; and a second computing deviceconfigured to send the one or more first messages. A computer-readablemedium may store instructions that, when executed, cause performance ofthe described method, additional operations and/or include theadditional elements.

FIG. 35 shows an example of a CSI-RS that may be mapped in time andfrequency domains. Each square shown in FIG. 35 may represent a resourceblock within a bandwidth of a cell. Each resource block may comprise anumber of subcarriers. A cell may have a bandwidth comprising a numberof resource blocks. A base station (e.g., a gNB in NR) may transmit oneor more Radio Resource Control (RRC) messages comprising CSI-RS resourceconfiguration parameters for one or more CSI-RS. One or more of thefollowing parameters may be configured by higher layer signaling foreach CSI-RS resource configuration: CSI-RS resource configurationidentity, number of CSI-RS ports, CSI-RS configuration (e.g., symbol andRE locations in a subframe), CSI-RS subframe configuration (e.g.,subframe location, offset, and periodicity in a radio frame), CSI-RSpower parameter, CSI-RS sequence parameter, CDM type parameter,frequency density, transmission comb, QCL parameters (e.g.,QCL-scramblingidentity, crs-portscount, mbsfn-subframeconfiglist,csi-rs-configZPid, qcl-csi-rs-configNZPid), and/or other radio resourceparameters.

FIG. 35 shows three beams that may be configured for a wireless device,for example, in a wireless device-specific configuration. Any number ofadditional beams (e.g., represented by the column of blank squares) orfewer beams may be included. Beam 1 may be allocated with CSI-RS 1 thatmay be transmitted in some subcarriers in a resource block (RB) of afirst symbol. Beam 2 may be allocated with CSI-RS 2 that may betransmitted in some subcarriers in an RB of a second symbol. Beam 3 maybe allocated with CSI-RS 3 that may be transmitted in some subcarriersin an RB of a third symbol. All subcarriers in an RB may not necessarilybe used for transmitting a particular CSI-RS (e.g., CSI-RS 1) on anassociated beam (e.g., beam 1) for that CSI-RS. By using frequencydivision multiplexing (FUM), other subcarriers, not used for beam 1 forthe wireless device in the same RB, may be used for other CSI-RStransmissions associated with a different beam for other wirelessdevices. Additionally or alternatively, by using time domainmultiplexing (TDM), beams used for a wireless device may be configuredsuch that different beams (e.g., beam 1, beam 2, and beam 3) for thewireless device may be transmitted using some symbols different frombeams of other wireless devices.

Beam management may use a device-specific configured CSI-RS. In a beammanagement procedure, a wireless device may monitor a channel quality ofa beam pair link comprising a transmitting beam by a base station (e.g.,a gNB in NR) and a receiving beam by the wireless device (e.g., a UE).If multiple CSI-RSs associated with multiple beams are configured, awireless device may monitor multiple beam pair links between the basestation and the wireless device.

A wireless device may transmit one or more beam management reports to abase station. A beam management report may indicate one or more beampair quality parameters, comprising, for example, one or more beamidentifications, RSRP, PMI, CQI, and/or RI, of a subset of configuredbeams.

A base station and/or a wireless device may perform a downlink L1/L2beam management procedure. One or more downlink L1/L2 beam managementprocedures may be performed within one or multiple transmission andreceiving points (TRPs), such as shown in FIG. 37A and FIG. 37B,respectively.

FIG. 36 shows examples of three beam management procedures, P1, P2, andP3. Procedure P1 may be used to enable a wireless device measurement ondifferent transmit (Tx) beams of a TRP (or multiple TRPs), for example,to support a selection of Tx beams and/or wireless device receive (Rx)beam(s) (shown as ovals in the top row and bottom row, respectively, ofP1). Beamforming at a TRP (or multiple TRPs) may include, for example,an intra-TRP and/or inter-TRP Tx beam sweep from a set of differentbeams (shown, in the top rows of P1 and P2, as ovals rotated in acounter-clockwise direction indicated by the dashed arrow). Beamformingat a wireless device (e.g., 3601 in FIG. 36 ), may include, for example,a wireless device Rx beam sweep from a set of different beams (shown, inthe bottom rows of P1 and P3, as ovals rotated in a clockwise directionindicated by the dashed arrow). Procedure P2 may be used to enable awireless device measurement on different Tx beams of a TRP (or multipleTRPs) (shown, in the top row of P2, as ovals rotated in acounter-clockwise direction indicated by the dashed arrow), for example,which may change inter-TRP and/or intra-TRP Tx beam(s). Procedure P2 maybe performed, for example, on a smaller set of beams for beam refinementthan in procedure P1. P2 may be a particular example of P1. Procedure P3may be used to enable a wireless device measurement on the same Tx beam(shown as oval in P3), for example, to change a wireless device Rx beamif the wireless device uses beamforming.

A wireless device (e.g., 3601 in FIG. 36 ) and/or a base station (e.g.,3602 in FIG. 36 ) may trigger a beam failure recovery mechanism. Thewireless device may trigger a beam failure recovery (BFR) requesttransmission, for example, if a beam failure event occurs. A beamfailure event may include, for example, a determination that a qualityof beam pair link(s) of an associated control channel is unsatisfactory.A determination of an unsatisfactory quality of beam pair link(s) of anassociated channel may be based on the quality falling below a thresholdand/or an expiration of a timer.

The wireless device may measure a quality of beam pair link(s) using oneor more reference signals (RS). One or more SS blocks, one or moreCSI-RS resources, and/or one or more demodulation reference signals(DM-RSs) of a PBCH may be used as a RS for measuring a quality of a beampair link. Each of the one or more CSI-RS resources may be associatedwith a CSI-RS resource index (CRI). A quality of a beam pair link may bebased on one or more of an RSRP value, reference signal received quality(RSRQ) value, and/or CSI value measured on RS resources. The basestation may indicate that an RS resource, for example, that may be usedfor measuring a beam pair link quality, is quasi-co-located (QCLed) withone or more DM-RSs of a control channel. The RS resource and the DM-RSsof the control channel may be QCLed when the channel characteristicsfrom a transmission via an RS to the wireless device, and the channelcharacteristics from a transmission via a control channel to thewireless device, are similar or the same under a configured criterion.

FIG. 37A shows an example of a beam failure event involving a singleTRP. A single TRP such as at a base station 3701 may transmit, to awireless device 3702, a first beam 3703 and a second beam 3704. A beamfailure event may occur if, for example, a serving beam, such as thesecond beam 3704, is blocked by a moving vehicle 3705 or otherobstruction (e.g., building, tree, land, or any object) and configuredbeams (e.g., the first beam 3703 and/or the second beam 3704), includingthe serving beam, are received from the single TRP. The wireless device3702 may trigger a mechanism to recover from beam failure when a beamfailure occurs.

FIG. 37B shows an example of a beam failure event involving multipleTRPs. Multiple TRPs, such as at a first base station 3706 and at asecond base station 3709, may transmit, to a wireless device 3708, afirst beam 3707 (e.g., from the first base station 3706) and a secondbeam 3710 (e.g., from the second base station 3709). A beam failureevent may occur when, for example, a serving beam, such as the secondbeam 3710, is blocked by a moving vehicle 3711 or other obstruction(e.g., building, tree, land, or any object) and configured beams (e.g.,the first beam 3707 and/or the second beam 3710) are received frommultiple TRPs. The wireless device 3608 may trigger a mechanism torecover from beam failure when a beam failure occurs.

A wireless device may monitor a PDCCH, such as a New Radio PDCCH(NR-PDCCH), on M beam pair links simultaneously, where M≥1 and themaximum value of M may depend at least on the wireless devicecapability. Such monitoring may increase robustness against beam pairlink blocking. A base station may transmit, and the wireless device mayreceive, one or more messages configured to cause the wireless device tomonitor NR-PDCCH on different beam pair link(s) and/or in differentNR-PDCCH OFDM symbol.

A base station may transmit higher layer signaling, and/or a MAC controlelement (MAC CE), that may comprise parameters related to a wirelessdevice Rx beam setting for monitoring NR-PDCCH on multiple beam pairlinks. A base station may transmit one or more indications of a spatialQCL assumption between a first DL RS antenna port(s) and a second DL RSantenna port(s). The first DL RS antenna port(s) may be for one or moreof a cell-specific CSI-RS, device-specific CSI-RS, SS block, PBCH withDM-RSs of PBCH, and/or PBCH without DM-RSs of PBCH. The second DL RSantenna port(s) may be for demodulation of a DL control channelSignaling for a beam indication for a NR-PDCCH (e.g., configuration tomonitor NR-PDCCH) may be via MAC CE signaling, RRC signaling, DCIsignaling, or specification-transparent and/or an implicit method, andany combination thereof.

For reception of unicast DL data channel, a base station may indicatespatial QCL parameters between DL RS antenna port(s) and DM-RS antennaport(s) of DL data channel. A base station may transmit DCI (e.g.,downlink grants) comprising information indicating the RS antennaport(s). The information may indicate the RS antenna port(s) which maybe QCLed with DM-RS antenna port(s). A different set of DM-RS antennaport(s) for the DL data channel may be indicated as a QCL with adifferent set of RS antenna port(s).

If a base station transmits a signal indicating a spatial QCL parametersbetween CSI-RS and DM-RS for PDCCH, a wireless device may use CSI-RSsQCLed with DM-RS for a PDCCH to monitor beam pair link quality. If abeam failure event occurs, the wireless device may transmit a beamfailure recovery request, such as by a determined configuration.

If a wireless device transmits a beam failure recovery request, forexample, via an uplink physical channel or signal, a base station maydetect that there is a beam failure event, for the wireless device, bymonitoring the uplink physical channel or signal. The base station mayinitiate a beam recovery mechanism to recover the beam pair link fortransmitting PDCCH between the base station and the wireless device. Thebase station may transmit one or more control signals, to the wirelessdevice, for example, after or in response to receiving the beam failurerecovery request. A beam recovery mechanism may be, for example, an L1scheme, or a higher layer scheme.

A base station may transmit one or more messages comprising, forexample, configuration parameters of an uplink physical channel and/or asignal for transmitting a beam failure recovery request. The uplinkphysical channel and/or signal may be based on at least one of thefollowing: a non-contention based PRACH (e.g., a beam failure recoveryPRACH or BFR-PRACH), which may use a resource orthogonal to resources ofother PRACH transmissions; a PUCCH (e.g., beam failure recovery PUCCH orBFR-PUCCH); and/or a contention-based PRACH resource. Combinations ofthese candidate signal and/or channels may be configured by a basestation.

A base station may respond a confirmation message to a wireless deviceafter receiving one or multiple BFR request. The confirmation messagemay include the CRI associated with the candidate beam the wirelessdevice indicates in the one or multiple BFR request. The confirmationmessage may be a L1 control information.

FIG. 38 shows example of a BFR procedure. A wireless device may receiveone or more RRC messages comprising BFR parameters 3801. The one or moreRRC messages may comprise an RRC message (e.g. RRC connectionreconfiguration message, or RRC connection reestablishment message, orRRC connection setup message). The wireless device may detect at leastone beam failure 3802 according to at least one of BFR parameters. Thewireless device may start a first timer if configured in response todetecting the at least one beam failure. The wireless device may selecta selected beam 3803 in response to detecting the at least one beamfailure. The selected beam may be a beam with good channel quality(e.g., RSRP, SINR, or BLER) from a set of candidate beams. The candidatebeams may be identified by a set of reference signals (e.g., SSBs, orCSI-RSs). The wireless device may transmit at least a first BFR signal3804 to a base station in response to the selecting the selected beam.The at least first BFR signal may be associated with the selected beam.The at least first BFR signal may be a preamble transmitted on a PRACHresource, or a SR signal transmitted on a PUCCH resource, or a beamindication transmitted on a PUCCH/PUSCH resource. The wireless devicemay transmit the at least first BFR signal with a transmission beamcorresponding to a receiving beam associated with the selected beam. Thewireless device may start a response window in response to transmittingthe at least first BFR signal. The response window may be a timer with avalue configured by the base station. If the response window is running,the wireless device may monitor a PDCCH in a first coreset 3805. Thefirst coreset may be associated with the BFR procedure. The wirelessdevice may monitor the PDCCH in the first coreset in condition oftransmitting the at least first BFR signal. The wireless device mayreceive first DCI via the PDCCH in the first coreset 3806 if theresponse window is running. The wireless device may consider the BFRprocedure successfully completed 3807 if receiving the first DCI via thePDCCH in the first coreset before the response window expires. Thewireless device may stop the first timer if configured in response tothe BFR procedure successfully being completed. The wireless device maystop the response window in response to the BFR procedure successfullybeing completed.

If the response window expires, and the wireless device does not receivethe DCI, the wireless device may increment a transmission number,wherein, the transmission number is initialized to a first number (e.g.,0) before the BFR procedure is triggered. If the transmission numberindicates a number less than the configured maximum transmission number3808, the wireless device may repeat one or more actions comprising atleast one of: a BFR signal transmission; starting the response window;monitoring the PDCCH; incrementing the transmission number if noresponse received during the response window is running. If thetransmission number indicates a number equal or greater than theconfigured maximum transmission number, the wireless device may declarethe BFR procedure is unsuccessfully completed 3809.

FIG. 39 shows DCI formats for an example of 20 MHz FDD operation with 2Tx antennas at the base station and no carrier aggregation in a longterm evolution (LTE)/long term evolution-advanced (LTE-A) system. Asshown in FIG. 37 , the DCI formats in the LTE/LTE-A system may compriseat least one of: DCI format 0; 1; 1A; 1B; 1C; 1D; 2; 2A; 2B; 2C; 2D; 3;3A; 4; 5; 6-0A; 6-0B; 6-1A; 6-1B; and/or 6-2. In an NR system, the DCIformats may comprise at least one of: DCI format 0_0/0_1 indicatingscheduling of PUSCH in a cell; DCI format 1_0/1_1 indicating schedulingof PDSCH in a cell; DCI format 2_0 notifying a group of UEs of slotformat; DCI format 2_1 notifying a group of UEs of PRB(s) and OFDMsymbol(s) where a wireless device may assume no transmission is intendedfor the wireless device; DCI format 2_2 indicating transmission of TPCcommands for PUCCH and PUSCH; and/or DCI format 2_3 indicatingtransmission of a group of TPC commands for SRS transmission by one ormore wireless devices.

A base station may transmit DCI via a PDCCH for scheduling decision andpower-control commends. More specifically, the DCI may comprise at leastone of: downlink scheduling assignments, uplink scheduling grants,power-control commands. The downlink scheduling assignments may compriseat least one of: PDSCH resource indication, transport format, HARQinformation, and control information related to multiple antennaschemes, a command for power control of the PUCCH used for transmissionof ACK/NACK in response to downlink scheduling assignments. The uplinkscheduling grants may comprise at least one of: PUSCH resourceindication, transport format, and HARQ related information, a powercontrol command of the PUSCH.

The different types of control information correspond to different DCImessage sizes. For example, supporting spatial multiplexing withnoncontiguous allocation of RBs in the frequency domain may require alarger scheduling message in comparison with an uplink grant allowingfor frequency-contiguous allocation only. The DCI may be categorizedinto different DCI formats, where a format corresponds to a certainmessage size and usage.

A wireless device may monitor one or more PDCCH candidates to detect oneor more DCI with one or more DCI format. The one or more PDCCH may betransmitted in common search space or wireless device-specific searchspace. A wireless device may monitor PDCCH with only a limited set ofDCI format, to save power consumption. For example, a normal UE may notbe required to detect a DCI with DCI format 6 which is used for an eMTCUE. The more DCI format to be detected, the more power be consumed atthe UE.

The one or more PDCCH candidates that a wireless device monitors may bedefined in terms of PDCCH UE-specific search spaces. A PDCCH UE-specificsearch space at CCE aggregation level L∈{1, 2, 4, 8} may be defined by aset of PDCCH candidates for CCE aggregation level L. For a DCI format, awireless device may be configured per serving cell by one or more higherlayer parameters a number of PDCCH candidates per CCE aggregation levelL.

In non-DRX mode operation, a wireless device may monitor one or morePDCCH candidate in control resource set q according to a periodicity ofW_(PDCCH, q) symbols that may be configured by one or more higher layerparameters for control resource set q.

The information in the DCI formats used for downlink scheduling may beorganized into different groups, with the field present varying betweenthe DCI formats, including at least one of: resource information,consisting of: carrier indicator (0 or 3 bits), RB allocation; HARQprocess number; MCS, NDI, and RV (for the first TB); MCS, NDI and RV(for the second TB); MIMO related information; PDSCH resource-elementmapping and QCI; Downlink assignment index (DAI); TPC for PUCCH; SRSrequest (e.g., 1 bit), triggering one-shot SRS transmission; ACK/NACKoffset; DCI format 0/1A indication, used to differentiate between DCIformat 1A and 0; and padding if necessary. The MIMO related informationmay comprise at least one of: PMI, precoding information, transportblock swap flag, power offset between PDSCH and reference signal,reference-signal scrambling sequence, number of layers, and/or antennaports for the transmission.

The information in the DCI formats used for uplink scheduling may beorganized into different groups, with the field present varying betweenthe DCI formats, including at least one of: resource information,comprising: carrier indicator, resource allocation type, RB allocation;MCS, NDI (for the first TB); MCS, NDI (for the second TB); phaserotation of the uplink DMRS; precoding information; CSI request,requesting an aperiodic CSI report; SRS request (2 bit), used to triggeraperiodic SRS transmission using one of up to three preconfiguredsettings; uplink index/DAI; TPC for PUSCH; DCI format 0/1A indication;and padding if necessary.

A base station may perform cyclic redundancy check (CRC) scrambling fora DCI, before transmitting the DCI via a PDCCH. The base station mayperform CRC scrambling by bit-wise addition (or Modulo-2 addition orexclusive OR (XOR) operation) of multiple bits of at least one wirelessdevice identifier (e.g., C-RNTI, CS-RNTI, TPC-CS-RNTI, TPC-PUCCH-RNTI,TPC-PUSCH-RNTI, SP CSI C-RNTI, SRS-TPC-RNTI, INT-RNTI, SFI-RNTI, P-RNTI,SI-RNTI, RA-RNTI, and/or MCS-C-RNTI) with the CRC bits of the DCI. Thewireless device may check the CRC bits of the DCI, when detecting theDCI. The wireless device may receive the DCI when the CRC is scrambledby a sequence of bits that is the same as the at least one wirelessdevice identifier. Otherwise, the wireless device may consider the DCIis detected with non-matching CRC and/or may ignore the DCI.

In an NR system or other systems, in order to support wide bandwidthoperation, a base station may transmit one or more PDCCH in differentcontrol resource sets. A base station may transmit one or more RRCmessage comprising configuration parameters of one or more controlresource sets. At least one of the one or more control resource sets maycomprise at least one of: a first OFDM symbol; a number of consecutiveOFDM symbols; a set of resource blocks; a CCE-to-REG mapping; and a REGbundle size, in case of interleaved CCE-to-REG mapping.

A base station (e.g., gNB) may configure a wireless device (e.g., a UE)with uplink (UL) bandwidth parts (BWPs) and downlink (DL) BWPs to enablebandwidth adaptation (BA) on a PCell. If carrier aggregation isconfigured, the base station may further configure the wireless devicewith at least DL BWP(s) (i.e., there may be no UL BWPs in the UL) toenable BA on an SCell. For the PCell, an initial active BWP may be afirst BWP used for initial access. For the SCell, a first active BWP maybe a second BWP configured for the wireless device to operate on theSCell upon the SCell being activated.

In paired spectrum (e.g. FDD), a base station and/or a wireless devicemay independently switch a DL BWP and an UL BWP. In unpaired spectrum(e.g. TDD), a gNB and/or a wireless device may simultaneously switch aDL BWP and an UL BWP.

A base station and/or a wireless device may switch a BWP betweenconfigured BWPs by means of a DCI or a BWP inactivity timer. If the BWPinactivity timer is configured for a serving cell, the base stationand/or the wireless device may switch an active BWP to a default BWP inresponse to an expiry of the BWP inactivity timer associated with theserving cell. The default BWP may be configured by the network.

For 1-DD systems, if configured with BA, one UL BWP for each uplinkcarrier and one DL BWP may be active at a time in an active servingcell. For TDD systems, one DL/UL BWP pair may be active at a time in anactive serving cell. Operating on the one UL BWP and the one DL BWP (orthe one DL/UL pair) may improve wireless device battery consumption.BWPs other than the one active UL BWP and the one active DL BWP that theUE may work on may be deactivated. On deactivated BWPs, the wirelessdevice may: not monitor PDCCH; and/or not transmit on PUCCH, PRACH, andUL-SCH.

A serving cell may be configured with at most a first number (e.g.,four) of BWPs. For an activated serving cell, there may be one activeBWP at any point in time.

A BWP switching for a serving cell may be used to activate an inactiveBWP and deactivate an active BWP at a time. The BWP switching may becontrolled by a PDCCH indicating a downlink assignment or an uplinkgrant. The BWP switching may be controlled by a BWP inactivity timer(e.g., bwp-InactivityTimer). The BWP switching may be controlled by aMAC entity in response to initiating a Random Access procedure. Uponaddition of an SpCell or activation of an SCell, one BWP may beinitially active without receiving a PDCCH indicating a downlinkassignment or an uplink grant. The active BWP for a serving cell may beindicated by RRC and/or PDCCH. In an example, for unpaired spectrum, aDL BWP may be paired with a UL BWP, and BWP switching may be common forboth UL and DL.

A wireless device may perform a first beam failure recovery on a PCell(e.g., in FR1) and a second beam failure recovery on a SCell (e.g., inFR2). If the wireless device switches to a power saving state from afull power state, performing the beam failure recovery for both PCelland SCell may not be power efficient. On the other hand, simply stoppingthe beam failure recovery for both a PCell and an SCell may cause beampair link failure and/or radio link failure. Beam failure recovery forcarrier aggregation in a power saving state may be improved, forexample, by continuing a beam failure recovery procedure. For example, awireless device, in response to switching to a power saving state from afull power state, may continue a first beam failure recovery on a PCelland stop (e.g., abort) a second beam failure recovery on an SCell. Bydoing so, the wireless device may maintain a beam pair link with a basestation (e.g., via the PCell), which may prevent beam pair link failureand/or radio link failure. The wireless device may (e.g., additionally)improve power consumption in the power saving state.

A wireless device may perform a beam failure recovery on a cell, forexample, if the wireless device is in a full power state. The wirelessdevice may monitor a downlink control channel on a control resource setfor receiving a response for a beam failure recovery request. Thewireless device may switch to a power saving state from the full powerstate. Keeping monitoring the downlink control channel on the controlresource set may not be power efficient. Stopping monitoring thedownlink control channel may cause beam pair link failure and/or radiolink failure. Beam failure recovery in a power saving state may beimproved, for example, by using different CORESETS. For example, awireless device may be configured with two CORESETS for beam failurerecovery, for example: a first CORESET for a full power state, and asecond CORESET for a power saving state. If the wireless device in thefull power state, the wireless device may monitor a downlink controlchannel, on the first CORESET configured for the full power state, forreceiving a response for the beam failure recovery request. If thewireless device switches to the power saving state, the wireless devicemay monitor the downlink control channel, on the second CORESETconfigured for the power saving state, for receiving the response forthe beam failure recovery request. By configuring two CORESETs for beamfailure recovery (e.g., a first having large resources for a full powerstate, and a second having smaller resources for a power saving state),the wireless device may reduce power consumption for beam failurerecovery in the power saving state and/or reduce possibility of beampair link failure and/or radio link failure. Additionally oralternatively, the wireless device may be configured with two referencesignals for beam failure recovery, for example: a first reference signalfor the full power state, and a second reference signal for the powersaving state. The wireless device may detect beam failure instances onthe first reference signal configured for the full power state. Ifswitching to the power saving state, the wireless device may continuethe beam failure detection based on the second reference signalconfigured for the power saving state. By using multiple referencesignals as described, the wireless device may determine whether a beamfailure occurs, and/or trigger a beam failure recovery procedure, morequickly than if multiple reference signals were not used.

A wireless device may perform a beam failure recovery on a cell, forexample, if the wireless device is in a full power state. The wirelessdevice may monitor a downlink control channel for receiving a responsefor a beam failure recovery request. The wireless device may receive acommand indicating switching to a power saving state from the full powerstate. Stop monitoring the downlink control channel may cause beam pairlink failure and/or radio link failure. On the other hand, ignoring thecommand may increase power consumption of the wireless device. Beamfailure recovery in a power saving state may be improved, for example,by delaying the switching to a different power state. For example, Awireless device, after receiving a command indicating switching from afull power state to a power saving state, may continue monitoring adownlink control channel for receiving a response for a beam failurerecovery request. The wireless device, in response to receiving theresponse for the beam failure recovery request, may switch from the fullpower state to the power saving state. By the wireless device delayingswitching to the power saving state if performing a beam failurerecovery and receiving a power saving command in overlapped timeduration, power consumption by the wireless device may be reduced and/ora beam failure recovery may be completed by the wireless device morequickly than if the wireless device does not delay the switching.Additionally or alternatively, the wireless device may be operating in apower saving state. If the wireless device is in the power saving state,the wireless device may trigger a beam failure recovery procedure. Basedon or in response to triggering the beam failure recovery procedure, thewireless device may switch automatically from the power saving state toa full power state. In the full power state, the wireless device maymonitor a downlink control channel for receiving a response for a beamfailure recovery request.

FIG. 40 shows an example of dynamic activating/deactivating power savingmode. A base station (e.g., 4002 in FIG. 40 ) may transmit to a wirelessdevice (e.g., 4001 in FIG. 40 ), one or more RRC messages comprisingconfiguration parameters of a power saving (e.g., PS in FIG. 40 ) mode.The one or more RRC messages may comprise one or more cell-specific orcell-common RRC messages (e.g., ServingCellConfig IE,ServingCellConfigCommon IE, MAC-CellGroupConfig IE). The one or more RRCmessages may comprise: RRC connection reconfiguration message (e.g.,RRCReconfiguration); RRC connection reestablishment message (e.g.,RRCRestablishment); and/or RRC connection setup message (e.g.,RRCSetup). The cell may be a primary cell (e.g., PCell), a PUCCHsecondary cell if secondary PUCCH group is configured, or a primarysecondary cell (e.g., PSCell) if dual connectivity is configured. Thecell may be identified by (or associated with) a cell specific identity(e.g., cell ID).

The configuration parameters may comprise parameters of at least onepower saving mode configuration on the cell. Each of the at least onepower saving mode configuration may be identified by a power saving modeconfiguration identifier (index, indicator, or ID).

A power saving mode of a power saving mode configuration may be based ona power saving signal (e.g., a wake-up signal as shown in FIG. 27A,and/or a go-to-sleep as shown in FIG. 27B). The parameters of a powersaving signal-based power saving mode configuration may comprise atleast one of: a signal format (e.g., numerology) of the power savingsignal; sequence generation parameters (e.g., a cell id, a virtual cellid, SS block index, or an orthogonal code index) for generating thepower saving signal; a window size of a time window indicating aduration if the power saving signal may be transmitted; a value of aperiodicity of the transmission of the power saving signal; a timeresource on which the power saving signal may be transmitted; afrequency resource on which the power saving signal may be transmitted;a BWP on which the wireless device may monitor the power saving signal;and/or a cell on which the wireless device may monitor the power savingsignal. The power saving signal may comprise at least one of: a SSblock; a CSI-RS; a DMRS; and/or a signal sequence (e.g., Zadoff-Chu, Msequence, or gold sequence).

A power saving mode may be based on a power saving channel (e.g., awake-up channel (WUCH)). The power saving channel may comprise adownlink control channel (e.g., a PDCCH) dedicated for the power savingmode. The parameters of a power saving channel-based power saving modeconfiguration may comprise at least one of: a time window indicating aduration if the base station may transmit a power saving information(e.g., a wake-up information, or a go-to-sleep information) via thepower saving channel; parameters of a control resource set (e.g., time,frequency resource and/or TCI state indication of the power savingchannel); a periodicity of the transmission of the power saving channel;a DCI format of the power saving information; a BWP on which thewireless device may monitor the power saving channel; and/or a cell onwhich the wireless device may monitor the power saving channel.

The wireless device in an RRC connected state may communicate with thebase station in a full function mode. In the full function mode, thewireless device may monitor PDCCHs continuously if a DRX operation isnot configured to the wireless device. In the full function mode, thewireless device may monitor the PDCCHs discontinuously by applying oneor more DRX parameters of the DRX operation if the DRX operation isconfigured (e.g., as shown in FIG. 25 or FIG. 26 ). In the full functionmode, the wireless device may: monitor PDCCHs; transmit SRS; transmit onRACH; transmit on UL-SCH; and/or receive DL-SCH.

As shown in FIG. 40 , the wireless device may communicate with the basestation in the full function mode. The base station may transmit to thewireless device, a first command (e.g., 1st command in FIG. 40 )indicating enabling a power saving (e.g., PS as shown in FIG. 40 )operation, for example, if a data service is suitable for the PS mode,or the wireless device may work in the PS mode due to a reducedavailable processing power at the wireless device. The first command maybe a DCI with a first DCI format (e.g., one of DCI format 0-0/0-1,1-0/1-1, or 2-0/2-1/2-2/2-3 already defined in 3GPP NR specifications)or a second DCI format (e.g., a new DCI format to be defined in future).The first command may be a MAC CE, or an RRC message. The wirelessdevice may, in response to receiving the first command, enable (oractivate) the PS mode and/or switch to the PS mode from the fullfunction mode. In the PS mode, the wireless device may: monitor for thePS signal/channel (e.g., WUS in FIG. 40 ); not transmitPUCCH/PUSCH/SRS/PRACH before detecting/receiving the PS signal/channel;not receive PDSCH before detecting/receiving the PS signal/channel; notmonitor PDCCHs before detecting/receiving the PS signal/channel; and/orstart monitoring the PDCCHs in response to detecting/receiving the PSsignal/channel

As shown in FIG. 40 , in response to switching to the PS mode, thewireless device may monitor a PS signal/channel (e.g., WUS in FIG. 40 )in a wakeup window. The PS signal/channel may be configured in the oneor more RRC messages. The wakeup window may be configured in the one ormore RRC messages. The wireless device may receive the PS signal/channelduring the wakeup window. In response to receiving the PSsignal/channel, the wireless device may monitor PDCCHs as configured(e.g., in RRC message or MAC CE) and transmit or receive data packetsbased on one or more DCIs via the PDCCHs. The wireless device may notreceive the PS signal/channel during the wakeup window. In response tonot receiving the PS signal/channel, the wireless device may skipmonitoring PDCCHs. In the PS mode, the wireless device may repeat themonitoring the PS signal/channel in one or more wakeup windows which mayperiodically occur according to one or more configured parameter of thePS mode.

As shown in FIG. 40 , the base station may transmit to the wirelessdevice, a second command (e.g., 2nd command in FIG. 40 ) indicatingdisabling (or deactivating) the PS mode. The base station may transmitthe second command in the wakeup window (e.g., which may periodicallyoccur in time domain according to one or more configuration parametersof the PS mode). The wireless device may receive the second command ifthe wireless device monitors the PS signal/channel during the wakeupwindow. The second command may be a DCI with a first DCI format (e.g.,one of DCI format 0-0/0-1, 1-0/1-1, or 2-0/2-1/2-2/2-3 already definedin 3GPP NR specifications) or a second DCI format (e.g., a new DCIformat to be defined in future). The second command may be a MAC CE, oran RRC message. The wireless device may, in response to receiving thesecond command, disable (or deactivate) the PS mode and/or switch to thefull function mode from the PS mode. In response to switching to thefull function mode as shown in FIG. 40 , the wireless device may monitorPDCCHs as configured. In response to switching to the full functionmode, the wireless device may monitor PDCCHs for detecting DCIs with CRCbits scrambled by at least one of: C-RNTI; P-RNTI; SI-RNTI; CS-RNTI;RA-RNTI; TC-RNTI; MCS-C-RNTI; TPC-PUCCH-RNTI; TPC-PUSCH-RNTI;TPC-SRS-RNTI; INT-RNTI; SFI-RNTI; and/or SP-CSI-RNTI. In response toswitching to the full function mode, the wireless device may transmitSRS; transmit on RACH; transmit on UL-SCH; and/or receive DL-SCH.

FIG. 41 shows an example of power saving mechanism. A base station(e.g., 4102 in FIG. 41 ) may transmit to a wireless device (e.g., 4101in FIG. 41 ), one or more RRC messages comprising first configurationparameters of a power saving (e.g., PS in FIG. 41 ) mode. The firstconfiguration parameters may indicate one or more PS parameters of aplurality of power saving modes. The one or more PS parameters of afirst power saving mode (e.g., PS mode 1 as shown in FIG. 41 ) mayindicate at least one of: one or more first search spaces and/or one ormore first control resource sets (e.g., SS1/CORESET1 in FIG. 41 ); oneor more first DCI formats (e.g., DCI format 0-0, 1-0, or any other DCIformat); and/or one or more first PS signal parameters (e.g., PS signalformat; periodicity; time/frequency location). The one or more PSparameters of a second power saving mode (e.g., PS mode 2 as shown inFIG. 41 ) may indicate at least one of: one or more second search spacesand/or one or more second control resource sets (e.g., SS1/CORESET1 andSS2/CORESET2 as shown in FIG. 41 ); one or more second DCI formats;and/or one or more second PS signal parameters.

The one or more RRC messages may further comprise second configurationparameters indicating one or more third search spaces and one or morethird control resource sets (e.g., SS1/CORESET1, SS2/CORSET2 . . . , andSSn/CORESETn as shown in FIG. 41 ); one or more third DCI formats.

The wireless device in an RRC connected state may communicate with thebase station in a full function mode. In the full function mode, thewireless device may monitor PDCCHs for the one or more third DCIformats, on the one or more third search spaces of the one or more thirdcontrol resource sets. In the full function mode, the wireless devicemay monitor the PDCCHs discontinuously by applying one or more DRXparameters of the DRX operation if the DRX operation is configured(e.g., as shown in FIG. 25 and/or FIG. 26 ). In the full function mode,the wireless device may: monitor PDCCHs; transmit SRS; transmit on RACH;transmit on UL-SCH; and/or receive DL-SCH.

As shown in FIG. 41 , the wireless device may communicate with the basestation in the full function mode. The base station may transmit to thewireless device, a first DCI (e.g., 1st DCI in FIG. 41 ) indicatingenabling a first power saving mode (e.g., PS mode 1 as shown in FIG. 41), for example, if a data service is suitable for the first PS mode, orthe wireless device may work in the first PS mode. The first DCI may betransmitted with a first DCI format (e.g., one of DCI formats 0-0/0-1,1-0/1-1, or 2-0/2-1/2-2/2-3 already defined in 3GPP NR specifications)or a second DCI format (e.g., a new DCI format to be defined in future).In response to receiving the first DCI, the wireless device may enable(or activate) the first PS mode and/or switch to the first PS mode fromthe full function mode. As shown in FIG. 41 , in the first PS mode, thewireless device may monitor a first PDCCH for at least one DCI with theone or more first DCI formats, on the one or more first search spaces ofthe one or more first control resource sets (e.g., SS1/CORESET1 as shownin FIG. 41 ). In the first PS mode, the wireless device may monitor thePS signal according to the one or more first PS signal parameters. Inthe first PS mode, the wireless device may not monitor PDCCHs on the oneor more second search spaces of the one or more second control resourcesets. In the first PS mode, the wireless device may not monitor PDCCHson the one or more third search spaces of the one or more third controlresource sets.

Similarly, as shown in FIG. 41 , the base station may transmit to thewireless device, a second DCI (e.g., 2nd DCI in FIG. 41 ) indicatingenabling (or activating) a second PS mode. (e.g., PS mode 2 as shown inFIG. 41 ). In response to receiving the second DCI, the wireless devicemay enable (or activate) the second PS mode and/or switch to the secondPS mode from the first PS mode. As shown in FIG. 41 , in the second PSmode, the wireless device may monitor a second PDCCH for at least oneDCI with the one or more second DCI formats, on the one or more secondsearch spaces of the one or more second control resource sets (e.g.,SS1/CORESET1, SS2/CORESET2 as shown in FIG. 41 ). In the second PS mode,the wireless device may monitor the PS signal according to the one ormore second PS signal parameters. In the second PS mode, the wirelessdevice may not monitor PDCCHs on the one or more first search spaces ofthe one or more first control resource sets. In the second PS mode, thewireless device may not monitor PDCCHs on the one or more third searchspaces of the one or more third control resource sets.

Similarly, as shown in FIG. 41 , the base station may transmit to thewireless device, a third DCI (e.g., 3rd DCI in FIG. 41 ) indicatingenabling (or activating) full function mode. In response to receivingthe third DCI, the wireless device may disable (or deactivate) the firstPS mode and the second PS mode. As shown in FIG. 41 , in the fullfunction mode, the wireless device may monitor a third PDCCH for atleast one DCI with the one or more third DCI formats, on the one or morethird search spaces of the one or more third control resource sets(e.g., SS1/CORESET1, SS2/CORESET2 . . . , SSn/CORESETn, as shown in FIG.41 ). In the full function mode, the wireless device may not monitorPDCCHs on the one or more first search spaces of the one or more firstcontrol resource sets. In the full function mode, the wireless devicemay not monitor PDCCHs on the one or more second search spaces of theone or more second control resource sets.

FIG. 42 shows an example of DRX based power saving mechanism. A basestation (e.g., 4202 in FIG. 42 ) may transmit to a wireless device(e.g., 4201 in FIG. 42 ), one or more RRC messages comprising firstconfiguration parameters of a plurality of DRX configurations. The firstconfiguration parameters of a first DRX configuration (e.g., 1st DRXconfiguration as shown in FIG. 42 ) may indicate: one or more firstsearch spaces (e.g., 1st SSs as shown in FIG. 42 ) and/or one or morefirst control resource sets (e.g., 1st CORESETs as shown in FIG. 42 );one or more first RNTIs (e.g., 1st RNTIs as shown in FIG. 42 ) of PDCCHcandidates monitoring; one or more first DCI formats (e.g., 1st DCIformats as shown in FIG. 42 ); one or more first DRX timers; and/or oneor more first PS signal parameters. The first configuration parametersof a second DRX configuration (e.g., 2nd DRX configuration as shown inFIG. 42 ) may indicate: one or more second search spaces (e.g., 2nd SSsas shown in FIG. 42 ) and/or one or more second control resource sets(e.g., 2nd CORESETs as shown in FIG. 42 ); one or more second RNTIs(e.g., 2nd RNTIs as shown in FIG. 42 ) of PDCCH candidates monitoring;one or more second DCI formats (e.g., 2nd DCI formats as shown in FIG.42 ); one or more second DRX timers; and/or one or more second PS signalparameters.

The one or more RRC messages may further comprise second configurationparameters indicating: one or more third search spaces (e.g., 3rd SSs asshown in FIG. 42 ) and one or more third control resource sets (e.g.,3rd CORESETs as shown in FIG. 42 ); one or more third DCI formats (e.g.,3rd DCI formats in FIG. 42 ); one or more third RNTIs (e.g., 3rd RNTIsas shown in FIG. 42 ) of PDCCH candidates monitoring.

As shown in FIG. 42 , the wireless device may communicate with the basestation in the full function mode. The base station may transmit to thewireless device, a first DCI (e.g., 1st DCI in FIG. 42 ) indicatingenabling the first DRX configuration (e.g., 1st DRX configuration asshown in FIG. 42 ). In response to receiving the first DCI, the wirelessdevice may enable (or activate) the first DRX configuration. As shown inFIG. 42 , with the first DRX configuration, the wireless device maymonitor a first PDCCH, based on one or more parameters of the first DRXconfiguration, for at least one DCI with the one or more first DCIformats based on the one or more first RNTIs, on the one or more firstsearch spaces of the one or more first control resource sets. Similarly,as shown in FIG. 42 , the base station may transmit to the wirelessdevice, a second DCI (e.g., 2nd DCI in FIG. 42 ) indicating enabling thesecond DRX configuration (e.g., 2nd DRX configuration as shown in FIG.42 ). In response to receiving the second DCI, the wireless device mayenable (or activate) the second DRX configuration. As shown in FIG. 42 ,with the second DRX configuration, the wireless device may monitor asecond PDCCH, based on one or more parameters of the second DRXconfiguration, for at least one DCI with the one or more second DCIformats based on the one or more second RNTIs, on the one or more secondsearch spaces of the one or more second control resource sets.

Similarly, as shown in FIG. 42 , the base station may transmit to thewireless device, a third DCI (e.g., 3rd DCI in FIG. 42 ) indicatingenabling (or activating) full function mode. In response to receivingthe third DCI, the wireless device may disable (or deactivate) the firstDRX configuration and/or the second DRX configuration. As shown in FIG.42 , in the full function mode, the wireless device may monitor a thirdPDCCH, for at least one DCI with the one or more third DCI formats basedon the one or more third RNTIs, on the one or more third search spacesof the one or more third control resource sets.

As shown in FIG. 41 and/or FIG. 42 , search spaces, control resourcesets, RNTIs, and/or DCI formats, with which a wireless device maymonitor a PDCCH in power saving mode, may be different from (orindependently/separately configured with) those search spaces, controlresource sets, RNTIs and/or DCI formats with which the wireless devicemay monitor the PDCCH in full function mode (or not in power savingmode). As shown in FIG. 41 and/or FIG. 42 , a first number of searchspaces, control resource sets, RNTIs, and/or DCI formats, with which awireless device may monitor a PDCCH in power saving mode, may be lessthan a second number of search spaces, control resource sets, RNTIsand/or DCI formats with which the wireless device may monitor the PDCCHin full function mode (or not in power saving mode). By performing theabove, a base station and/or a wireless device may control powerconsumption appropriately according to whether the wireless device isworking in power saving mode or in full function mode.

Before a base station transmits a command indicating a wireless deviceswitching to power saving mode (e.g., as shown in FIG. 40 , FIG. 41and/or FIG. 42 ), the wireless device may be in a process of a beamfailure recovery (e.g., BFR) procedure. After a base station transmits acommand indicating a wireless device switching to power saving mode(e.g., as shown in FIG. 40 , FIG. 41 and/or FIG. 42 ), the wirelessdevice may initiate a beam failure recovery (e.g., BFR) procedure. Awireless device may initiate a RA procedure for a BFR procedure for acell if a number of beam failure instances (e.g. contiguous) aredetected. The cell may be a PCell or a SCell. The cell may be a cellworking in licensed band or a cell working in unlicensed band. A beamfailure instance may occur if quality of a beam pair link is lower thana configured threshold. For example, a beam failure instance may occurif the RSRP value or SINR value of a beam pair link is lower than afirst threshold, or the BLER (block error rate) of the beam pair link ishigher than a second threshold. Sporadic beam failure instance may notnecessarily trigger the RA procedure for the BFR procedure. The RAprocedure may be a contention-based RA procedure or a contention-free RAprocedure, or a combined contention-based and contention free RAprocedure. In combined contention-based and contention free RAprocedure, the wireless device may switch from contention-based RAprocedure to contention-free procedure for the BFR procedure, ifswitching condition(s) is met. The switching conditions may comprise atleast one of: candidate beam not being selected; and/or an expiry of abeam failure recovery timer.

FIG. 43 shows an example of a BFR procedure. A wireless device (e.g.,4301 in FIG. 43 ) may receive from a base station (e.g., 4302 in FIG. 43), one or more RRC messages comprising one or more configurationparameters of a BFR procedure. The one or more configuration parametersof the BFR procedure may comprise at least a first threshold for beamfailure detection; at least a second threshold for selecting a beam(s);a first control resource set (e.g., coreset) associated with (ordedicated to) the BFR procedure. The first coreset may comprise multipleRBs in the frequency domain, at least a symbol in the time domain. Thefirst coreset may be associated with the BFR procedure. The wirelessdevice may monitor at least a first PDCCH in the first coreset inresponse to transmitting a BFR signal indicating the beam failure. Thewireless device may not monitor the first PDCCH in the first coreset inresponse to not transmitting the BFR signal. In The base station may nottransmit a PDCCH in the first coreset if the base station does notreceive the BFR signal on an uplink resource. The base station maytransmit a PDCCH in a second coreset if the base station does notreceive the BFR signal. The second coreset, in which the wireless devicemay monitor a PDCCH before the BFR procedure is triggered, is differentfrom the first coreset.

The one or more configuration parameters of the BFR procedure mayindicate a first set of RSs for beam failure detection; and/or one ormore PRACH resources associated with a second set of RSs (beams) forcandidate beam selection. The one or more PRACH resources may compriseat least one of: one or more preambles; and/or one or moretime/frequency resources. Each RS of the second set of RSs may beassociated with a preamble, a timer resource and/or a frequency resourceof one of the one or more PRACH resources.

The one or more configuration parameters of the BFR procedure mayindicate one or more PUCCH or scheduling request (SR) resources. The oneor more PUCCH or SR resource may comprise at least one of: timeallocation; frequency allocation; cyclic shift; orthogonal cover code;and/or a spatial setting.

The first set of RSs may be one or more first CSI-RSs or one or morefirst SSBs. The second set of RSs may be one or more second CSI-RSs orone or more second SSBs. A BFR signal may be a PRACH preambletransmitted via a time/frequency resource of a PRACH resource. A BFRsignal may be a PUCCH/SR transmitted on a PUCCH/SR resource.

The one or more configuration parameters of the BFR procedure maycomprise at least one of: a first number (e.g.,beamFailureInstanceMaxCount) indicating a number of beam failureinstances which may trigger a RA procedure for the BFR; a first timervalue of a beam failure detection timer (e.g.,beamFailureDetectionTimer), after an expiry of which, the wirelessdevice may reset a beam failure detection counter (e.g., BFI_COUNTER); asecond timer value of a beam failure recovery timer (e.g.,beamFailureRecoveryTimer) indicating a duration during which acontention-free RA for the BFR procedure may be performed; a secondnumber (e.g., preambleTransMax) indicating an allowed number of BFRsignal transmissions; a third timer value of a response window (e.g.,ra-ResponseWindow) indicating a duration during which the wirelessdevice may receive a response from a base station.

The wireless device may perform beam failure detections, after receivingthe RRC messages. The physical layer of the wireless device may measurethe first set of RSs. The physical layer may indicate one or more beamfailure instance or one or more beam non-failure instance periodicallyto the MAC entity of the wireless device, based on the at least firstthreshold. The physical layer may indicate a beam failure instance ifthe measured quality (e.g., RSRP or SINR) of at least one of the firstset of RSs is lower than the at least first threshold. The physicallayer may indicate a beam non-failure instance if the measured quality(e.g., RSRP or SINR) of at least one of the first set of RSs is equal toor higher than the at least first threshold. The physical layer may skipindicating a beam non-failure instance if the measured quality (e.g.,RSRP or SINR) of at least one of the first set of RSs is equal to orhigher than the at least first threshold. The periodicity of theindication may be a value configured by the base station or be same asthe periodicity of transmission of the first set of RSs.

The MAC entity of the wireless device may set a beam failure detectioncounter (e.g., BFI_COUNTER) to a first value (e.g., one) in response toreceiving a first beam failure indication from the physical layer. Ifreceiving a contiguous second beam failure indication, the MAC entitymay increment the beam failure detection counter (e.g., BFI_COUNTER)(e.g., by one). If receiving a third beam non-failure indication, theMAC entity may reset the beam failure detection counter (e.g.,BFI_COUNTER) to a second value (e.g., zero).

If receiving a first beam failure indication from the physical layer,the MAC entity may start the beam failure detection timer (e.g.,beamFailureDetectionTimer) based on the first timer value.

A timer (e.g., beamFailureDetectionTimer, beamFailureRecoveryTimer, orra-ResponseWindow) may be running if it is started, until it is stoppedor until it expires; otherwise the timer may not be running A timer maybe started if it is not running A timer may be restarted if it isrunning A timer may be started or restarted from its initial value. Atimer may be implemented as a count-down timer from a first timer valuedown to a value (e.g., zero). The timer may be implemented as a count-uptimer from a value (e.g., zero) up to a first timer value. The timer maybe implemented as a down-counter from a first counter value down to avalue (e.g., zero). The timer may be implemented as a count-up counterfrom a value (e.g., zero) up to a first counter value.

If receiving a second beam failure indication from the physical layer,the MAC entity may increment the beam failure detection counter (e.g.,BFI_COUNTER) by a number (e.g., 1) and/or restart the beam failuredetection timer. If the beam failure detection timer expires, the MACentity may reset the beam failure detection counter (e.g., BFI_COUNTER)to an initial value.

As shown in FIG. 43 , if the beam failure detection counter indicates avalue equal to or greater than the first number (e.g.,beamFailureInstanceMaxCount), the MAC entity may initiate a RA (e.g.,contention-based or contention free) procedure for a BFR. If the beamfailure detection counter indicates a value equal to or greater than thefirst number (e.g., beamFailureInstanceMaxCount), the MAC entity maystart the beam failure recovery timer (e.g., beamFailureRecoveryTimer)based on the second timer value.

If initiating the RA procedure for the BFR, the MAC entity may performat least one of: resetting the beam failure detection counter to aninitial value (e.g., zero); resetting the beam failure detection timer;and/or indicating to the physical layer to stop beam failure instanceindication. The MAC entity may ignore the beam failure instanceindication, if triggering the RA procedure for the BFR.

The MAC entity may request the physical layer to indicate at least abeam and/or the quality of the at least beam, in response to startingthe beam failure recovery timer or initiating the RA procedure for theBFR. The physical layer of the wireless device may measure at least oneof the second set of RSs. The physical layer may select at least a beambased on the at least second threshold. The at least beam may beidentified by a CSI-RS resource index, or an SSB index. The physicallayer may select a beam if the measured quality (e.g., RSRP or SINR) ofan RS associated the beam is greater than the at least second threshold.

As shown in FIG. 43 , the MAC entity may select at least a BFR signal(e.g., 1st preamble as shown in FIG. 43 ), based on the at least beamand instruct the physical layer to transmit the at least BFR signal to abase station, in response to receiving the indication of the at leastbeam from the physical layer. The at least BFR signal may be a PRACHpreamble associated with the at least beam. The at least BFR signal maybe a PUCCH/SR signal.

The wireless device may start monitoring a PDCCH for receiving a DCI asa response to the transmitted BFR signal, at least in the first coreset,after a time period since transmitting the at least BFR signal. The timeperiod (e.g., k as shown in FIG. 43 ) may be a fixed period (e.g., fourslots), or a configured value by an RRC message. The wireless device maystart the response window (e.g., ra-ResponseWindow or response-window asshown in FIG. 43 ) with a third timer value after the time period sincetransmitting the at least BFR signal. The wireless device may monitorthe PDCCH in the first coreset during the response window.

The wireless device may receive a DCI via the PDCCH at least in thefirst coreset in the response window. The wireless device may considerthe BFR procedure successfully completed in response to receiving theDCI via the PDCCH at least in the first coreset in the response window.

The wireless device may set a BFR transmission counter (e.g.,PREAMBLE_TRANSMISSION_COUNTER) to a value (e.g., one) in response to anexpiry of the response window and not receiving the DCI. In response toan expiry of the response window and not receiving the DCI, the wirelessdevice may perform one or more actions comprising at least one of:transmitting at least a second BFR signal (e.g., 2nd preamble as shownin FIG. 43 ); starting the response window; and/or monitoring the PDCCHfor a response to the at least second BFR signal; incrementing the BFRtransmission counter (e.g., PREAMBLE_TRANSMISSION_COUNTER) by a number(e.g., one) in response to an expiry of the response window and notreceiving the response. The wireless device may repeat the one or moreactions until the BFR procedure is successfully completed, or the beamfailure recovery timer expires. If the beam failure recovery timerexpires, the wireless device may continue the BFR by implementing acontention-based RA procedure. A contention-based RA procedure may beimplemented based on an example of FIG. 12 . Based on one or moreparameters of the contention-based RA procedure, the wireless device maytransmit at least a third preamble (e.g., 3rd preamble in FIG. 43 ) inresponse to the BFR transmission counter (e.g.,PREAMBLE_TRANSMISSION_COUNTER) less than or equal to the second number(e.g., preambleTransMax). The wireless device may consider the RAprocedure for the BFR is unsuccessfully completed if the BFRtransmission counter (e.g., PREAMBLE_TRANSMISSION_COUNTER) reaches anumber greater than the second number (e.g., preambleTransMax).

A wireless device may be in a process of a BFR during which, thewireless device may receive from a base station a command indicatingactivation/enabling of a power saving mode. The command may be adownlink signal (e.g., a signal sequence), a DCI (e.g., transmitted viaa PDCCH), a MAC CE, and/or an RRC message. The wireless device, byimplementing existing power saving technologies, may miss detecting aresponse to a preamble transmitted by the wireless device. The wirelessdevice, by implementing existing power saving technologies, may increasepower consumption (e.g., trying to complete beam failure recoveryprocedure), although in a power saving mode. Existing power savingtechnologies and/or beam failure recovery technologies may increasepower consumption of a wireless device and/or delay of a beam failurerecovery. Existing power saving technologies and/or beam failurerecovery technologies may cause misalignment between a wireless deviceand a base station regarding a power saving mode of the wireless deviceand/or a beam link status between the wireless device and the basestation. Existing power saving technologies and/or beam failure recoverytechnologies may increase data transmission latency, and/or probabilityof communication link broken between a base station and a wirelessdevice. At least some examples described herein may provide methods andmechanisms to improve power consumption of a wireless device, delay of abeam failure recovery, data transmission latency, system spectrumefficiency, and/or uplink interferences to other wireless devices. Itshould be noted that the term power saving mode may be referred to usingother terminologies, such as power saving operation, power savingprocedure, power saving state, etc. It should also be noted thattechnologies of the power saving mode in one or more examples may bedifferent from a 3GPP Ra. 12 PSM technology. The 3GPP Ra. 12 PSMtechnology may be applied to a wireless device in RRC idle state, andmay not be applied to the wireless device in RRC connected state. Thetechnologies of the power saving mode in one or more examples may beapplied to a wireless device in RRC connected state, RRC inactive state,and/or RRC idle state.

FIG. 44 shows an example of improved BFR procedure if power saving modeis supported. A base station (e.g., 4402 in FIG. 44 ) may transmit to awireless device (e.g., 4401 in FIG. 44 ), one or more RRC messagescomprising configuration parameters of a power saving mode (e.g., PSmode in FIG. 44 ). The one or more RRC messages may comprise one or morecell-specific or cell-common RRC messages (e.g., ServingCellConfig IE,ServingCellConfigCommon IE, MAC-CellGroupConfig IE). The one or more RRCmessages may comprise: RRC connection reconfiguration message (e.g.,RRCReconfiguration); RRC connection reestablishment message (e.g.,RRCRestablishment); and/or RRC connection setup message (e.g.,RRCSetup). The cell may be a primary cell (e.g., PCell), a PUCCHsecondary cell if secondary PUCCH group is configured, or a primarysecondary cell (e.g., PSCell) if dual connectivity is configured, or asecondary cell.

The configuration parameters may comprise parameters of at least onepower saving mode configuration on the cell. Each of the at least onepower saving mode configuration may be identified by a power saving modeconfiguration identifier (index, indicator, or ID).

A power saving mode of a power saving mode configuration may be based ona power saving signal (e.g., a wake-up signal as shown in FIG. 27A,and/or a go-to-sleep as shown in FIG. 27B). The parameters of the powersaving mode configuration may comprise at least one of: a signal format(e.g., numerology) of the power saving signal; sequence generationparameters (e.g., a cell id, a virtual cell id, SS block index, or anorthogonal code index) for generating the power saving signal; a windowsize of a time window indicating a duration if the power saving signalmay be transmitted; a value of a periodicity of the transmission of thepower saving signal; a time resource on which the power saving signalmay be transmitted; a frequency resource on which the power savingsignal may be transmitted; a BWP on which the wireless device maymonitor the power saving signal; and/or a cell on which the wirelessdevice may monitor the power saving signal. The power saving signal maycomprise at least one of: a SS block; a CSI-RS; a DMRS; and/or a signalsequence (e.g., Zadoff-Chu, M sequence, or gold sequence).

A power saving mode may be based on a power saving channel (e.g., awake-up channel (WUCH)). The power saving channel may comprise adownlink control channel (e.g., a PDCCH) dedicated for the power savingmode. The parameters of the power saving mode configuration may compriseat least one of: a time window indicating a duration if the base stationmay transmit a power saving information (e.g., a wake-up information, ora go-to-sleep information) via the power saving channel; parameters of acontrol resource set (e.g., time, frequency resource and/or TCI stateindication of the power saving channel); a periodicity of thetransmission of the power saving channel; a DCI format of the powersaving information; a BWP on which the wireless device may monitor thepower saving channel; and/or a cell on which the wireless device maymonitor the power saving channel.

A power saving mode may be implemented by dynamically changing PDCCHsmonitoring, for example, a smaller number of search spaces/controlresources sets/RNTIs/DCI formats being configured for PDCCH monitoringin a power saving mode than the case in full function mode, as shown inFIG. 41 . A power saving mode may be implemented by dynamicallyactivating/enabling different DRX configurations, as shown in FIG. 42 .

The wireless device in an RRC connected state may communicate with thebase station in a full function mode. It should be noted that the termfull function mode may be referred to using other technologies, such asfull function state, normal access mode, normal access state. In thefull function mode, the wireless device may monitor PDCCHs continuouslyif a DRX operation is not configured to the wireless device. In thenormal access mode, the wireless device may monitor the PDCCHsdiscontinuously by applying one or more DRX parameters of the DRXoperation if the DRX operation is configured (e.g., as shown in FIG. 25or FIG. 26 ). In the full function mode, the wireless device may:monitor PDCCHs; transmit SRS; transmit on RACH; transmit on UL-SCH;and/or receive DL-SCH. In the full function mode, the wireless devicemay perform beam failure detection and/or initiate a RA for a BFR ifdetecting a number of beam failure instance. The beam failure detectionand the RA for the BFR may be implemented as shown in one or moreexamples of FIG. 38 and/or FIG. 43 .

As shown in FIG. 44 , the wireless device may initiate an RA for a BFRin response to a number of beam failure instances being detected. Thewireless device may receive a first command indicating an activation (orenabling) of a power saving mode. The wireless device may receive afirst command indicating an activation (or enabling) of a power savingmode of a plurality of power saving modes, if the plurality of powersaving modes are configured. The first command may comprise at least oneof: a downlink signal; a DCI transmitted via a PDCCH; a MAC CE; and/oran RRC message.

As shown in FIG. 44 , in response to receiving the first commandindicating an activation of a power saving mode, the wireless device mayabort (or stop) an ongoing RA procedure for the BFR. The ongoing RAprocedure for the BFR may be initiated for a first cell (e.g., a PCell),or a secondary cell (e.g., SCell). In response to receiving the firstcommand, the wireless device may skip monitoring, for a response to apreamble for the BFR, a PDCCH on a search space/control resource setdedicated for the BFR. In response to receiving the first command, thewireless device may reset a beam failure detection counter (e.g.,BFI_COUNTER) to an initial value (e.g., 0). In response to receiving thefirst command, the wireless device may stop transmitting BFR signals forthe BFR and/or may reset a preamble transmission counter (e.g.,PREAMBLE_TRANSMISSION_COUNTER) to an initial value (e.g., 0). Inresponse to receiving the first command, the wireless device may stopone or more timers for the BFR. The one or more timers may comprise atleast one of: a beam failure detection timer (e.g.,beamFailureDetectionTimer); a beam failure recovery timer (e.g.,beamFailureRecoveryTimer); and/or a beam failure recovery responsewindow (e.g., ra-ResponseWindow). In response to receiving the firstcommand, the wireless device may reduce PDCCH monitoring, for example bymonitoring a smaller number of search spaces, control resource sets,RNTIs and/or DCI formats than the case in full function mode.

As shown in FIG. 44 , the base station may transmit to the wirelessdevice, a second command indicating disabling (or deactivation) of thepower saving mode. As shown in FIG. 44 , the wireless device may restart(or re-initiate) the RA for the BFR in response to receiving the secondcommand. In response to receiving the second command, the wirelessdevice may monitor, for a response to a preamble, a PDCCH on the searchspace/control resource set dedicated for the BFR. In response toreceiving the second command, the wireless device may switch from thepower saving mode to a full function mode. In the full function mode,the wireless device may: monitor PDCCHs as configured and/or required;transmit SRS; transmit on RACH; transmit on UL-SCH; and/or receiveDL-SCH.

As shown in FIG. 44 , a wireless device may abort a BFR procedure if thewireless device is indicated by a base station to switch to a powersaving mode. Examples described herein may improve power consumption ofa wireless device, delay of a beam failure recovery, data transmissionlatency, system spectrum efficiency, and/or uplink interferences toother wireless devices.

FIG. 45 shows an example of improved BFR procedure if power saving modeis supported. A base station (e.g., 4502 in FIG. 45 ) may transmit to awireless device (e.g., 4501 in FIG. 45 ), one or more RRC messagescomprising first configuration parameters of a power saving mode (e.g.,PS mode in FIG. 45 ) and/or second configuration parameters of a beamfailure recovery (e.g., BFR in FIG. 45 ). The cell may be a primary cell(e.g., PCell), a PUCCH secondary cell if secondary PUCCH group isconfigured, or a primary secondary cell (e.g., PSCell) if dualconnectivity is configured, or a secondary cell.

The first configuration parameters for the power saving mode may be thesame as or similar to one or more examples of FIG. 44 . The power savingmode may be the same as or similar to the one or more examples of FIG.44 . The second configuration parameters for the BFR may be same orsimilar as one or more examples of FIG. 43 and/or FIG. 44 .

As shown in FIG. 45 , the wireless device may monitor first PDCCHs(e.g., 1st PDCCHs in FIG. 45 ) on first search spaces and/or firstcontrol resource sets (e.g., 1st SS/CORESET as shown in FIG. 45 ). Thewireless device may perform a first beam failure detection based on themonitoring the first PDCCHs. The first beam failure detection based onthe monitoring the first PDCCHs may be implemented based on one or moreexamples of FIG. 38 and/or FIG. 43 . The wireless device may receive acommand indicating enabling a power saving mode (e.g., PS mode in FIG.45 ) before detecting a beam failure instance. In response to receivingthe command, the wireless device may monitor second PDCCHs (e.g., 2ndPDCCHs in FIG. 45 ) on second search spaces and/or second controlresource sets (e.g., 2nd SS/CORESET in FIG. 45 ). The wireless devicemay perform a second beam failure detection based on the monitoring thesecond PDCCHs. The second beam failure detection based on the monitoringthe second PDCCHs may be implemented based on one or more examples ofFIG. 38 and/or FIG. 43 . First RSs for a first beam failure detection ina first mode (e.g., a full function mode, or a mode before receiving thecommand indicating an activation/enabling of a power saving mode) may bedifferent from second RSs for a second beam failure detection in asecond mode (e.g., a power saving mode, or a mode after receiving thecommand indicating an activation/enabling of a power saving mode).

As shown in FIG. 45 , a physical layer of the wireless device mayindicate a number of beam failure instance indications (e.g., BFIindications in FIG. 45 ) to a higher layer (e.g., a MAC layer and/or alayer 3) of the wireless device starting from T0. The number of beamfailure instance indications may be based on the monitoring the secondPDCCHs (e.g., or second RSs configured with the second PDCCHs for aBFR). If the number of beam failure instance indications is greater thana configured value (e.g., beamFailureInstanceMaxCount) at T1, thewireless device may initiate a RA for a BFR. The RA for the BFR may beimplemented as one or more examples of FIG. 38 and/or FIG. 43 .

As shown in FIG. 45 , a wireless device may perform a BFR procedure ifthe wireless device is indicated by a base station to switch to a powersaving mode. The BFR procedure in the power saving mode may beimplemented based on one or more BFR parameters configured for the powersaving mode. One or more first BFR parameters configured for a first BFRin the power saving mode may be independently or separately configuredfrom one or more second BFR parameters for a second BFR in a fullfunction mode. Examples described herein may improve delay of a beamfailure recovery if a wireless device is working in a power saving mode.

FIG. 46 shows an example of improved beam failure recovery procedure ifa power saving mode is supported. A base station (e.g., 4602 in FIG. 46) may transmit to a wireless device (e.g., 4601 in FIG. 46 ), one ormore RRC messages comprising first configuration parameters of a powersaving mode (e.g., PS mode in FIG. 46 ) and/or second configurationparameters of a beam failure recovery (e.g., BFR in FIG. 46 ). The cellmay be a primary cell (e.g., PCell), a PUCCH secondary cell if secondaryPUCCH group is configured, or a primary secondary cell (e.g., PSCell) ifdual connectivity is configured, or a secondary cell.

The first configuration parameters for the power saving mode may be thesame as or similar to one or more examples of FIG. 44 . The power savingmode may be the same as or similar to the one or more examples of FIG.44 . The second configuration parameters for the BFR may be the same asor similar to one or more examples of FIG. 43 and/or FIG. 44 .

As shown in FIG. 46 , the wireless device may monitor first PDCCHs(e.g., 1st PDCCHs in FIG. 46 ) on first search spaces and/or firstcontrol resource sets (e.g., 1st SS/CORESET as shown in FIG. 46 ). Thewireless device may perform a first beam failure detection based on themonitoring the first PDCCHs (or first RSs configured with the firstPDCCHs for a BFR). The first beam failure detection based on themonitoring the first PDCCHs (or may be implemented based on one or moreexamples of FIG. 38 and/or FIG. 43 . A physical layer of the wirelessdevice may indicate a first number of beam failure instance indications(e.g., 1st BFI indications in FIG. 46 ) to a higher layer (e.g., a MAClayer and/or a layer 3) of the wireless device, starting from T0.

As shown in FIG. 46 , the wireless device may receive a commandindicating enabling a power saving mode (e.g., PS mode in FIG. 46 ) atT1, wherein T1 occurs a number of symbols/slots/subframes after T0. Inresponse to receiving the command, the wireless device may monitorsecond PDCCHs (e.g., 2nd PDCCHs in FIG. 46 ). The wireless device mayperform a second beam failure detection based on the monitoring thesecond PDCCHs (or second RSs configured with the second PDCCHs for aBFR). The second beam failure detection based on the monitoring thesecond PDCCHs may be implemented based on one or more examples of FIG.38 and/or FIG. 43 . The physical layer of the wireless device mayindicate a second number of beam failure instance indications (e.g., 2ndBFI indications in FIG. 46 ) to a higher layer (e.g., a MAC layer and/ora layer 3) of the wireless device, starting from T1.

As shown in FIG. 46 , in response to receiving the command indicating anactivation/enabling of a power saving mode, the wireless device mayreset a beam failure detection counter (e.g., BFI_COUNTER) to an initialvalue and/or start counting the beam failure detection counter from aninitial value based on the second beam failure detection. In response toreceiving the command indicating an activation/enabling of a powersaving mode, the wireless device may reset a beam failure detectiontimer (e.g., beamFailureDetectionTimer) to an initial value. In responseto receiving the command indicating an activation/enabling of a powersaving mode, the wireless device may keep running (or may not reset) thebeam failure detection timer. In response to receiving the commandindicating an activation/enabling of a power saving mode, the wirelessdevice may keep counting (or may not reset) the beam failure detectioncounter (e.g., even if the first RSs for the first beam failuredetection are different from the second RSs for the second beam failuredetection). In response to receiving the command enabling the PS mode,the wireless device may keep monitoring the first RSs for the first beamfailure detection and/or keep counting the beam failure detectioncounter based on the first RSs.

As shown in FIG. 46 , the wireless device may initiate a RA for a BFRbased on the first BFI indications and/or the second BFI indications.The first BFI indications may be based on the first beam failuredetection. The second BFI indications may be based on the second beamfailure detection. The RA for the BFR may be implemented based on one ormore examples of FIG. 38 and/or FIG. 43 .

As shown in FIG. 46 , a wireless device may continue a BFR procedure ifthe wireless device is indicated by a base station to switch to a powersaving mode from a full function mode. The BFR procedure in the powersaving mode may be implemented based on one or more BFR parametersconfigured for the power saving mode. One or more first BFR parametersconfigured for a first BFR in the power saving mode may be independentlyor separately configured from one or more second BFR parameters for asecond BFR in a full function mode. Examples described herein mayimprove delay of a beam failure recovery if a wireless device is workingin a power saving mode.

FIG. 47 shows an examples of improved BFR in power saving mode. A basestation (e.g., 4702 in FIG. 47 ) may transmit to a wireless device(e.g., 4701 in FIG. 47 ), one or more RRC messages comprising firstconfiguration parameters of a power saving mode (e.g., PS mode in FIG.47 ) and/or second configuration parameters of a beam failure recovery(e.g., BFR in FIG. 47 ). The first configuration parameters for thepower saving mode may be the same as or similar to one or more examplesof FIG. 44 . The power saving mode may be the same as similar to the oneor more examples of FIG. 44 . The second configuration parameters forthe BFR may be the same as or similar to one or more examples of FIG. 43and/or FIG. 44 .

As shown in FIG. 47 , the wireless device may monitor first PDCCHs(e.g., 1st PDCCHs in FIG. 47 ) on first search spaces and/or firstcontrol resource sets (e.g., 1st SS/CORESET as shown in FIG. 47 ). Thewireless device may perform a beam failure detection based on themonitoring the first PDCCHs (or first RSs configured with the firstPDCCHs for a BFR). The beam failure detection based on the monitoringthe first PDCCHs (or may be implemented based on one or more examples ofFIG. 38 and/or FIG. 43 ). A physical layer of the wireless device mayindicate a number of beam failure instance indications (e.g., BFIindications in FIG. 47 ) to a higher layer (e.g., a MAC layer and/or alayer 3) of the wireless device, starting from T0.

As shown in FIG. 47 , in response to the number of beam failure instanceindications being equal to or greater than a configured value (e.g.,beamFailureInstanceMaxCount), the wireless device may initiate a RAprocedure for a BFR and/or start a beam failure recovery timer (e.g.,beamFailureRecoveryTimer), at T1. T1 may occur a number ofsymbols/slots/subframes after T0. The wireless device may receive acommand indicating enabling a power saving mode (e.g., PS mode in FIG.47 ) at T2, wherein T2 occurs a number of symbol/slots/subframes afterT1. The wireless device may receive a command indicating enabling apower saving mode, before the wireless device transmits a BFR signal forthe BFR. In response to receiving the command, the wireless device mayabort the RA for the BFR. In response to receiving the command, thewireless device may abort transmitting (or may skip transmitting) a BFRsignal for the BFR. In response to receiving the command, the wirelessdevice may stop the beam failure recovery timer. In response toreceiving the command, the wireless device may monitor second PDCCHs onsecond search spaces/control resource sets (e.g., 2nd SS/CORESET in FIG.47 ).

As shown in FIG. 47 , a wireless device may abort a BFR procedure if thewireless device is indicated by a base station to switch to a powersaving mode. Examples described herein may improve power consumption ofa wireless device and/or uplink interferences to other wireless devices.

FIG. 48 shows an example of improved beam failure recovery if a powersaving mode is supported. A base station (e.g., 4802 in FIG. 48 ) maytransmit to a wireless device (e.g., 4801 in FIG. 48 ), one or more RRCmessages comprising first configuration parameters of a power savingmode (e.g., PS in FIG. 48 ) and/or second configuration parameters of abeam failure recovery (e.g., BFR in FIG. 48 ). The first configurationparameters for the power saving mode may be the same as or similar toone or more examples of FIG. 44 . The power saving mode may be the sameas or similar to the one or more examples of FIG. 44 . The secondconfiguration parameters for the BFR may be the same as or similar toone or more examples of FIG. 43 and/or FIG. 44 .

As shown in FIG. 48 , the wireless device may monitor first PDCCHs(e.g., 1st PDCCHs in FIG. 48 ) on first search spaces and/or firstcontrol resource sets (e.g., 1st SS/CORESET as shown in FIG. 48 ). Thewireless device may perform a beam failure detection based on themonitoring the first PDCCHs (or first RSs configured with the firstPDCCHs for a BFR). The beam failure detection based on the monitoringthe first PDCCHs (or may be implemented based on one or more examples ofFIG. 38 and/or FIG. 43 ). A physical layer of the wireless device mayindicate a number of beam failure instance indications (e.g., BFIindications in FIG. 48 ) to a higher layer (e.g., a MAC layer and/or alayer 3) of the wireless device, starting from T0.

As shown in FIG. 48 , in response to the number of beam failure instanceindications being equal to or greater than a configured value (e.g.,beamFailureInstanceMaxCount), the wireless device may initiate a RAprocedure for a BFR and/or start a beam failure recovery timer (e.g.,beamFailureRecoveryTimer), at T1. T1 may occur a number ofsymbols/slots/subframes after T0.

As shown in FIG. 48 , in response to initiating the RA for the BFR, thewireless device may transmit a BFR signal at T2. T2 may occur a numberof symbols/slots/subframes after T1. The wireless device may monitor,for a response to the BFR signal, a second PDCCH on a second searchspace/control resource set (e.g., 2nd SS/CORESET as shown in FIG. 48 )dedicated for the BFR.

As shown in FIG. 48 , the wireless device may receive a commandindicating enabling a power saving mode (e.g., PS mode in FIG. 48 ),after the wireless device transmits the BFR signal for the BFR. Thewireless device may receive a command indicating enabling a power savingmode in a time period during which the wireless device is monitoring thesecond PDCCH for the response to the BFR signal. In response toreceiving the command, the wireless device may ignore the command and/ormay continue the BFR, for example, by keeping monitoring the secondPDCCH for the response to the BFR signal. In response to receiving thecommand, the wireless device may switch to the power saving mode, exceptthat the wireless device keeps monitoring the second PDCCH for theresponse to the BFR signal. In response to receiving the command, thewireless device may switch to the power saving mode, monitor a thirdPDCCH for the response to the BFR signal, and/or stop monitor the secondPDCCH for the response to the BFR signal. The third PDCCH may beconfigured to be monitored by the wireless device in the power savingmode.

As shown in FIG. 48 , a wireless device may continue a BFR procedure ina power saving mode if the wireless device is indicated by a basestation to switch to the power saving mode. Examples described hereinmay improve delay of a beam failure recovery and power consumption ofthe wireless device.

FIG. 49 shows an example of improved beam failure recovery if a powersaving mode is supported. A wireless device (e.g., 4901 in FIG. 49 ) mayreceive a command indicating an activation/enabling of a power savingmode (e.g., PS mode in FIG. 49 ) from a base station (e.g., 4092). Inresponse to receiving the command, the wireless device may switch to thepower saving mode. The power saving mode may comprise a first powersaving mode implemented based on one or more examples of FIG. 40 . Inthe first power saving mode, the wireless device may: monitor a wakeupsignal/channel (e.g., WUS in FIG. 49 ); not monitor first PDCCHs beforereceiving a wakeup signal or before receiving a wakeup command via thewakeup channel; monitor the first PDCCHs in response to receiving thewakeup signal or in response to receiving the wakeup command via thewakeup channel. The power saving mode may comprise second power savingmode by one or more examples of FIG. 41 and/or FIG. 42 .

As shown in FIG. 49 , the wireless device may initiate a RA procedurefor a BFR in the power saving mode. In response to initiating the RAprocedure for the BFR in the power saving mode, the wireless device mayswitch from the power saving mode to a full function mode. In responseto switching to the full function mode, the wireless device may: monitorPDCCHs; transmit SRS; transmit on RACH; transmit on UL-SCH; and/orreceive DL-SCH. In response to initiating the RA procedure for the BFRin the power saving mode, the wireless device may: transmit a BFR signalfor the RA procedure for the BFR; monitoring, for a response to the BFRsignal, a PDCCH on a search space/control resource set dedicated for theBFR.

As shown in FIG. 49 , a wireless device may automatically switch to afull function mode if the wireless device initiates a RA for a BFR in apower saving mode. Examples described herein may improve delay of a beamfailure recovery, data transmission latency, and/or system spectrumefficiency.

In response to receiving the command enabling the power saving mode, thewireless device may switch to the power saving mode. The wirelessdevice, in response to receiving the command, may not perform a beamfailure detection and/or may not initiate a RA for a BFR (e.g., for aPCell and/or a SCell). The wireless device, in response to receiving thecommand, may disable the beam failure detection and/or may disable theRA procedure for the BFR. BFR configuration parameters of a BFR may notbe applied if the wireless device is in a power saving mode. Examplesdescribed herein may improve power consumption of a wireless device.

FIG. 50 shows an example of improved BFR procedure if a power savingmode is supported. A wireless device (e.g., 5001 in FIG. 50 ) mayreceive a command indicating an activation/enabling of a power savingmode (e.g., PS mode in FIG. 50 ) from a base station (e.g., 5002). Inresponse to receiving the command, the wireless device may switch to thepower saving mode. The power saving mode may comprise a first powersaving mode implemented based on one or more examples of FIG. 40 . Thepower saving mode may comprise second power saving mode by one or moreexamples of FIG. 41 and/or FIG. 42 .

As shown in FIG. 50 , the wireless device may initiate a RA procedurefor a BFR in the power saving mode. In response to initiating the RAprocedure for the BFR in the power saving mode, the wireless device mayswitch from the power saving mode to a full function mode. In responseto switching to the full function mode, the wireless device may: monitorPDCCHs; transmit SRS; transmit on RACH; transmit on UL-SCH; and/orreceive DL-SCH. In response to initiating the RA procedure for the BFRin the power saving mode, the wireless device may: transmit a BFR signalfor the RA procedure for the BFR; monitoring, for a response to the BFRsignal, a PDCCH on a search space/control resource set dedicated for theBFR.

As shown in FIG. 50 , the wireless device may receive a DCI as theresponse to the BFR signal in a time period during which the wirelessdevice is monitoring the PDCCH on the search space/control resource setdedicated for the BFR. In response to receiving the DCI, the wirelessdevice may complete the BFR and may switch to the power saving mode(e.g., automatically). The power saving mode may comprise the firstpower saving mode and/or the second power saving mode. The first powersaving mode may be implemented based on one or more examples of FIG. 40. The second power saving mode may be implemented based on one or moreexamples of FIG. 41 and/or FIG. 42 .

As shown in FIG. 50 , the wireless device may switch to a full functionmode if the wireless device initiates a RA procedure for a BFR in a timeperiod during which the wireless device is in a power saving mode. Thewireless device may automatically switch to the power saving mode afterthe wireless device complete the RA procedure for the BFR. Examplesdescribed herein may improve delay of a beam failure recovery, powerconsumption of the wireless device, and/or downlink spectrum efficiency.

FIG. 51 shows an example of improved BFR if multiple cells areconfigured. A base station (e.g., 5102 in FIG. 51 ) may transmit to awireless device (e.g., 5101 in FIG. 51 ), one or more RRC messagescomprising first configuration parameters of a power saving mode (e.g.,PS mode in FIG. 51 ). The one or more RRC messages may comprise: RRCconnection reconfiguration message (e.g., RRCReconfiguration); RRCconnection reestablishment message (e.g., RRCRestablishment); and/or RRCconnection setup message (e.g., RRCSetup). The one or more RRC messagesmay comprise one or more cell-specific or cell-common RRC messages(e.g., ServingCellConfig IE, ServingCellConfigCommon IE,MAC-CellGroupConfig IE). The one or more RRC messages may comprisesecond configuration parameters of a first beam failure recovery (e.g.,BFR in FIG. 51 ) for a first cell and a second BFR for a second cell.The first cell may be a primary cell (e.g., PCell), a PUCCH secondarycell if secondary PUCCH group is configured, or a primary secondary cell(e.g., PSCell) if dual connectivity is configured. The second cell maybe a secondary cell.

As shown in FIG. 51 , the wireless device may initiate, for the firstcell, a first RA procedure for a first BFR, in response to detecting afirst number of beam failure instances on the first cell. The first RAprocedure may be performed on the first cell, for example, based on oneor more examples of FIG. 44 . The wireless device may initiate a secondRA procedure for a second BFR for the second cell, in response todetecting a second number of beam failure instances on the second cell.The second RA procedure may be performed on the first cell and/or thesecond cell, for example, based on one or more examples of FIG. 44 . Thefirst RA procedure may overlap in time with the second RA procedure. Thefirst RA procedure may not overlap in time with the second RA procedure.

As shown in FIG. 51 , the wireless device may receive a commandindicating an activation of a power saving mode. The command maycomprise at least one of: a downlink signal sequence; a DCI transmittedon a PDCCH; a MAC CE; and/or an RRC message. The command may betransmitted on the first cell. The command may be transmitted on thesecond cell. In response to receiving the command, the wireless devicemay continue the first RA procedure for the first cell, if the first RAprocedure is ongoing if the wireless device receives the command. Thewireless device may continue the first RA procedure for the first cellby implementing one or more examples of FIG. 45 , FIG. 46 , FIG. 47 ,FIG. 48 , FIG. 49 and/or FIG. 50 . In response to receiving the command,the wireless device may abort the second RA procedure for the secondcell, if the second RA procedure is ongoing if the wireless devicereceives the command.

The wireless device may receive the command indicating an activation ofthe power saving mode, before the wireless device initiates the first RAprocedure for the first BFR for the first cell and/or the second RAprocedure for the second BFR for the second cell. In response toreceiving the command, the wireless device may switch to the powersaving mode. In response to receiving the command, the wireless devicemay perform, for the first cell, a first beam failure detection and/orinitiate, for the first cell, a first RA procedure for a first BFR ifdetecting a number of beam failure instances on the first cell. Inresponse to receiving the command, the wireless device may disable beamfailure recovery procedure for the second cell. In response to receivingthe command, the wireless device may not perform, for the second cell, asecond beam failure detection and/or may not initiate, for the secondcell, a second RA procedure for a second BFR.

As shown in FIG. 51 , a wireless device may perform beam failurerecovery procedure on a PCell and may not perform beam failure recoveryprocedure on a SCell if the wireless device works in a power savingmode. Examples described herein may improve power consumption of awireless device if: beam failure recovery procedures are configured on aPCell and a SCell; and a power saving mode is configured.

A wireless device may initiate a random access procedure for a beamfailure recovery of a cell. The wireless device may transmit, inresponse to initiating the random access procedure for the beam failurerecovery, a preamble via radio resource of a random access channel. Inresponse to the transmitting, the wireless device may, monitor for aresponse to the preamble, first downlink control channel candidates infirst search spaces of a first control resource set of the cell. Thewireless device may receive a downlink signal indicating action of apower saving mode. The wireless device may, in response to receiving thedownlink signal, activate the power saving mode. In response toactivating the power saving mode, the wireless device may stop (orabort) the random access procedure for the beam failure recovery on thecell. In response to activating the power saving mode, the wirelessdevice may stop monitoring the first downlink control channel candidatesin the first search spaces of the first control resource set of thecell. In response to activating the power saving mode, the wirelessdevice may monitor second downlink control channel candidates in secondsearch spaces of a second control resource set. The wireless device mayreceive one or more first downlink control information on the seconddownlink control channel candidates. The wireless device may transmit orreceive data packets based on the one or more first downlink controlinformation.

A wireless device may initiate a random access procedure for a beamfailure recovery of a cell. The wireless device may transmit, inresponse to initiating the random access procedure for the beam failurerecovery of the cell, a preamble via radio resources of a random accesschannel. The wireless device may monitor, for a response to thepreamble, first downlink control channel candidates in first searchspaces of first control resource set of the cell. The wireless devicemay receive a downlink signal indicating activation of a power savingmode. If the power saving mode is activated, the wireless device may:stop the monitoring the first downlink control channel candidates in thefirst search spaces of the first control resource set; monitor seconddownlink control channel candidates in second search spaces of secondcontrol resource set of the cell. The wireless device may activate, inresponse to receiving the downlink signal, the power saving mode. Inresponse to activating the power saving mode, the wireless device may:stop the random access procedure for the beam failure recovery of thecell; and monitor the second downlink control channel candidates in thesecond search spaces.

A wireless device may receive from a base station, a first downlinksignal indicating activation of a power saving mode. The wireless devicemay activate, in response to the first downlink signal, the power savingmode, wherein the power saving mode comprise skipping monitoringdownlink control channel candidates in first search spaces of a firstcontrol resource set of a cell. The wireless device may initiate arandom access procedure for a beam failure recovery in response todetecting a number of beam failure instances. The wireless device maydeactivate, in response to the initiating the random access procedure,the power saving mode. The wireless device may transmit, in response todeactivating the power saving mode and the initiating the random accessprocedure, a preamble for the beam failure recovery of the cell.

A wireless device may receive from a base station, configurationparameters indicating: a first random access procedure of a first beamfailure recovery on a first cell; and a second random access procedureof a second beam failure recovery on a second cell. The wireless devicemay receive a first downlink signal indicating activation of a powersaving mode. The wireless device may activate, in response to the firstdownlink signal, the power saving mode. In response to activating thepower saving mode, the wireless device may: initiate the first randomaccess procedure of the first beam recovery on the first cell, inresponse to detecting a number of beam failure instances on the firstcell; and/or not initiate the second random access procedure of thesecond beam resource on the second cell in response to detecting anumber of beam failure instances on the second cell.

A wireless device may receive, from a base station that may transmit,one or more messages comprising: first parameters of a first beamfailure recovery procedure on a first cell; and second parameters of asecond beam failure recovery procedure on a second cell. The wirelessdevice may receive, from the base station that may transmit, a downlinksignal indicating transitioning from a first power state to a secondpower state. The wireless device may transition to, in response to thedownlink signal, the second power state. During the second power state,the wireless device may: continue a first beam failure recoveryprocedure on the first cell; and/or stop a second beam failure recoveryprocedure for the second cell. The first cell may be a primary cell. Thesecond cell may be a secondary cell. The stopping the second beamfailure recovery procedure may comprise stopping detecting beam failureinstances on the second cell. The stopping the second beam failurerecovery procedure may comprise stopping monitoring a downlink controlchannel for a response of a beam failure recovery request for the secondcell. The stopping the second beam failure recovery procedure maycomprise stopping transmitting a beam failure recovery request for thesecond cell. The beam failure recovery request may comprise at least oneof: a preamble; and/or a scheduling request via an uplink controlchannel resource. The downlink signal may comprise a medium accesscontrol (MAC) control element (CE). The downlink signal may comprise apower saving indication via a power saving channel. The power savingchannel may be on the first cell. The power saving channel may be on thesecond cell. The first power state may be a first time duration if thewireless device: monitors a first downlink control channel, on the firstcell, for receiving a first downlink assignment or a first uplink grant;and/or monitors a second downlink control channel, on the second cell orfor the second cell, for receiving a second downlink assignment or asecond uplink grant. The second power state may be a second timeduration if the wireless device: stops monitoring the first downlinkcontrol channel on the first cell; stops monitoring the second downlinkcontrol channel on the second cell or for the second cell; and/ormonitors a power saving channel for receiving a power saving indication.The first parameters may comprise: a first number for detecting beamfailure instances; configuration parameters of one or more random accesschannel resources for the first beam failure recovery procedure; and/ora first control resource set for reception of a response of a beamfailure recovery request for the first beam failure recovery procedurein the first power state. The first parameters may comprise a secondcontrol resource set for reception of the response of the beam failurerequest for the first beam failure recovery procedure in the secondpower state. The wireless device may trigger the first beam failurerecovery procedure on the first cell in response to detecting the firstnumber of beam failure instances on the first cell. The wireless devicemay transmit a beam failure recovery request via a first one of the oneor more random access channel resources; monitor a downlink controlchannel on the first control resource set for receiving a response forthe transmission of the beam failure recovery request; and/or incrementa beam failure recovery transmission counter in response to notreceiving the response in a monitoring window. The continuing the firstbeam failure recovery procedure may comprise transmitting the beamfailure recovery request via a second one of the one or more randomaccess channel resources. The continuing the first beam failure recoveryprocedure may comprise monitoring a downlink control channel on thesecond control resource set for receiving a response for thetransmission of the beam failure recovery request. The continuing thefirst beam failure recovery procedure may comprise incrementing the beamfailure recovery transmission counter in response to not receiving theresponse in the monitoring window.

Additionally or alternatively, the wireless device may trigger a beamfailure recovery procedure in response to detecting a number of beamfailure instances on a cell in a first power state; transmit a beamfailure recovery request in response to the triggering; monitor, on afirst control resource set of the cell in the first power state, a firstdownlink control channel for receiving a response to the transmittingthe beam failure recovery request; receive, via power saving channel, apower saving indication indicating a second power state of the cell;monitor, on a second control resource set of the cell in the secondpower state, a second downlink control channel for receiving theresponse to the transmitting the beam failure recovery request; and/orreceive the response during the monitoring the second downlink controlchannel. The first power state may be a first time duration if thewireless device monitors a downlink control channel for receiving adownlink assignment or an uplink grant. The second power state may be asecond time duration if the wireless device: stops monitoring thedownlink control channel; and/or monitors a power saving channel forreceiving a power saving indication. The wireless device may receive oneor more configuration parameters of the beam failure recovery procedure.The configuration parameters may indicate: the first control resourceset for the beam failure recovery procedure of the cell in the firstpower state; and/or the second control resource set for the beam failurerecovery procedure of the cell in the second power state.

Additionally or alternatively, the wireless device may detect a beamfailure instance based on a first reference signal of a cell in a firstpower state; increment a beam failure counter based on the detecting thebeam failure instance; receive, via a power saving channel, a powersaving indication indicating a second power state of the cell; incrementthe beam failure counter in response to detecting a beam failureinstance based on a second reference signal of the cell in the secondpower state; trigger a beam failure recovery procedure based on the beamfailure counter reaching a first value; and/or transmit a beam failurerecovery request in response to the triggering the beam failure recoveryprocedure. The wireless device may receive one or more configurationparameters of the beam failure recovery procedure. The configurationparameters may indicate: the first reference signal for the beam failurerecovery procedure of the cell in the first power state; and/or thesecond reference signal for the beam failure recovery procedure of thecell in the second power state.

Additionally or alternatively, the wireless device may trigger a beamfailure recovery procedure in response to detecting a number of beamfailure instances on a cell in a first power state; transmit a beamfailure recovery request in response to the triggering the beam failurerecovery procedure; receive a power saving indication indicating asecond power state of the cell; monitor a downlink control channel forreceiving a response to the transmitting the beam failure recoveryrequest; receive the response during the monitoring the downlink controlchannel; and/or transition, based on the power saving indication andafter the receiving the response, the cell from the first power state tothe second power state. The first power state may be a first timeduration when the wireless device monitors a downlink control channelfor receiving a downlink assignment or an uplink grant. The second powerstate may be a second time duration if the wireless device: stopsmonitoring the downlink control channel; and/or monitors a power savingchannel for receiving a power saving indication.

Additionally or alternatively, the wireless device may trigger a beamfailure recovery procedure in response to detecting a number of beamfailure instances on the cell in a first power state; switch, based onthe triggering the beam failure recovery procedure, the cell from thefirst power state to the second power state; and/or transmit a beamfailure recovery request via the cell in the second power state. Thewireless device may monitor a downlink control channel for receiving aresponse to the transmitting the beam failure recovery request; and/orreceive the response during the monitoring the downlink control channel.The first power state may be a first time duration if the wirelessdevice: stops monitoring a downlink control channel; and/or monitors apower saving channel for receiving a power saving indication. The secondpower state may be a second time duration, for example, if the wirelessdevice monitors the downlink control channel for receiving a downlinkassignment or an uplink grant.

FIG. 52 shows example elements of a computing device that may be used toimplement any of the various devices described herein, including, e.g.,the base station 120A and/or 120B, the wireless device 110 (e.g., 110Aand/or 110B), or any other base station, wireless device, or computingdevice described herein. The computing device 5200 may include one ormore processors 5201, which may execute instructions stored in therandom-access memory (RAM) 4103, the removable media 5204 (such as aUniversal Serial Bus (USB) drive, compact disk (CD) or digital versatiledisk (DVD), or floppy disk drive), or any other desired storage medium.Instructions may also be stored in an attached (or internal) hard drive5205. The computing device 5200 may also include a security processor(not shown), which may execute instructions of one or more computerprograms to monitor the processes executing on the processor 5201 andany process that requests access to any hardware and/or softwarecomponents of the computing device 5200 (e.g., ROM 5202, RAM 5203, theremovable media 5204, the hard drive 5205, the device controller 5207, anetwork interface 5209, a GPS 5211, a Bluetooth interface 5212, a WiFiinterface 5213, etc.). The computing device 5200 may include one or moreoutput devices, such as the display 5206 (e.g., a screen, a displaydevice, a monitor, a television, etc.), and may include one or moreoutput device controllers 5207, such as a video processor. There mayalso be one or more user input devices 5208, such as a remote control,keyboard, mouse, touch screen, microphone, etc. The computing device5200 may also include one or more network interfaces, such as a networkinterface 5209, which may be a wired interface, a wireless interface, ora combination of the two. The network interface 5209 may provide aninterface for the computing device 5200 to communicate with a network5210 (e.g., a RAN, or any other network). The network interface 5209 mayinclude a modem (e.g., a cable modem), and the external network 5210 mayinclude communication links, an external network, an in-home network, aprovider's wireless, coaxial, fiber, or hybrid fiber/coaxialdistribution system (e.g., a DOCSIS network), or any other desirednetwork. Additionally, the computing device 5200 may include alocation-detecting device, such as a global positioning system (GPS)microprocessor 5211, which may be configured to receive and processglobal positioning signals and determine, with possible assistance froman external server and antenna, a geographic position of the computingdevice 5200.

The example in FIG. 52 may be a hardware configuration, although thecomponents shown may be implemented as software as well. Modificationsmay be made to add, remove, combine, divide, etc. components of thecomputing device 5200 as desired. Additionally, the components may beimplemented using basic computing devices and components, and the samecomponents (e.g., processor 5201, ROM storage 5202, display 5206, etc.)may be used to implement any of the other computing devices andcomponents described herein. For example, the various componentsdescribed herein may be implemented using computing devices havingcomponents such as a processor executing computer-executableinstructions stored on a computer-readable medium, as shown in FIG. 52 .Some or all of the entities described herein may be software based, andmay co-exist in a common physical platform (e.g., a requesting entitymay be a separate software process and program from a dependent entity,both of which may be executed as software on a common computing device).

The disclosed mechanisms herein may be performed if certain criteria aremet, for example, in a wireless device, a base station, a radioenvironment, a network, a combination of the above, and/or the like.Example criteria may be based on, for example, wireless device and/ornetwork node configurations, traffic load, initial system set up, packetsizes, traffic characteristics, a combination of the above, and/or thelike. If the one or more criteria are met, various examples may be used.It may be possible to implement examples that selectively implementdisclosed protocols.

A base station may communicate with a mix of wireless devices. Wirelessdevices and/or base stations may support multiple technologies, and/ormultiple releases of the same technology. Wireless devices may have somespecific capability(ies) depending on wireless device category and/orcapability(ies). A base station may comprise multiple sectors. A basestation communicating with a plurality of wireless devices may refer tobase station communicating with a subset of the total wireless devicesin a coverage area. Wireless devices referred to herein may correspondto a plurality of wireless devices of a particular LTE or 5G releasewith a given capability and in a given sector of a base station. Aplurality of wireless devices may refer to a selected plurality ofwireless devices, and/or a subset of total wireless devices in acoverage area. Such devices may operate, function, and/or perform basedon or according to drawings and/or descriptions herein, and/or the like.There may be a plurality of base stations or a plurality of wirelessdevices in a coverage area that may not comply with the disclosedmethods, for example, because those wireless devices and/or basestations perform based on older releases of LTE or 5G technology.

One or more features described herein may be implemented in acomputer-usable data and/or computer-executable instructions, such as inone or more program modules, executed by one or more computers or otherdevices. Generally, program modules include routines, programs, objects,components, data structures, etc. that perform particular tasks orimplement particular abstract data types when executed by a processor ina computer or other data processing device. The computer executableinstructions may be stored on one or more computer readable media suchas a hard disk, optical disk, removable storage media, solid statememory, RAM, etc. The functionality of the program modules may becombined or distributed as desired. The functionality may be implementedin whole or in part in firmware or hardware equivalents such asintegrated circuits, field programmable gate arrays (FPGA), and thelike. Particular data structures may be used to more effectivelyimplement one or more features described herein, and such datastructures are contemplated within the scope of computer executableinstructions and computer-usable data described herein.

Many of the elements in examples may be implemented as modules. A modulemay be an isolatable element that performs a defined function and has adefined interface to other elements. The modules may be implemented inhardware, software in combination with hardware, firmware, wetware(i.e., hardware with a biological element) or a combination thereof, allof which may be behaviorally equivalent. For example, modules may beimplemented as a software routine written in a computer languageconfigured to be executed by a hardware machine (such as C, C++,Fortran, Java, Basic, Matlab or the like) or a modeling/simulationprogram such as Simulink, Stateflow, GNU Octave, or Lab VIEWMathScript.Additionally or alternatively, it may be possible to implement modulesusing physical hardware that incorporates discrete or programmableanalog, digital and/or quantum hardware. Examples of programmablehardware may comprise: computers, microcontrollers, microprocessors,application-specific integrated circuits (ASICs); field programmablegate arrays (FPGAs); and complex programmable logic devices (CPLDs).Computers, microcontrollers, and microprocessors may be programmed usinglanguages such as assembly, C, C++ or the like. FPGAs, ASICs, and CPLDsmay be programmed using hardware description languages (HDL), such asVHSIC hardware description language (VHDL) or Verilog, which mayconfigure connections between internal hardware modules with lesserfunctionality on a programmable device. The above-mentioned technologiesmay be used in combination to achieve the result of a functional module.

A non-transitory tangible computer readable media may compriseinstructions executable by one or more processors configured to causeoperations of multi-carrier communications described herein. An articleof manufacture may comprise a non-transitory tangible computer readablemachine-accessible medium having instructions encoded thereon forenabling programmable hardware to cause a device (e.g., a wirelessdevice, wireless communicator, a wireless device, a base station, andthe like) to allow operation of multi-carrier communications describedherein. The device, or one or more devices such as in a system, mayinclude one or more processors, memory, interfaces, and/or the like.Other examples may comprise communication networks comprising devicessuch as base stations, wireless devices or user equipment (wirelessdevice), servers, switches, antennas, and/or the like. A network maycomprise any wireless technology, including but not limited to,cellular, wireless, WiFi, 4G, 5G, any generation of 3GPP or othercellular standard or recommendation, wireless local area networks,wireless personal area networks, wireless ad hoc networks, wirelessmetropolitan area networks, wireless wide area networks, global areanetworks, space networks, and any other network using wirelesscommunications. Any device (e.g., a wireless device, a base station, orany other device) or combination of devices may be used to perform anycombination of one or more of steps described herein, including, forexample, any complementary step or steps of one or more of the abovesteps.

Although examples are described above, features and/or steps of thoseexamples may be combined, divided, omitted, rearranged, revised, and/oraugmented in any desired manner Various alterations, modifications, andimprovements will readily occur to those skilled in the art. Suchalterations, modifications, and improvements are intended to be part ofthis description, though not expressly stated herein, and are intendedto be within the spirit and scope of the descriptions herein.Accordingly, the foregoing description is by way of example only, and isnot limiting.

What is claimed is:
 1. A method comprising: receiving, by a wirelessdevice, beam failure recovery (BFR) configuration parameters of asecondary cell; stopping, during a time period in which the secondarycell is in a dormant state, monitoring of a downlink control channel onthe secondary cell; and performing, during the time period in which thesecondary cell is in the dormant state and the wireless device is notmonitoring the downlink control channel on the secondary cell, a BFRprocedure.
 2. The method of claim 1, further comprising: receivingdownlink control information (DCI) indicating a transition, of thesecondary cell, from a non-dormant state to a dormant state, and whereinthe stopping monitoring of the downlink control channel is based on theDCI.
 3. The method of claim 1, further comprising: receiving a commandindicating activation of a power saving mode, and wherein the stoppingmonitoring of the downlink control channel is based on the command. 4.The method of claim 1, further comprising: monitoring, while thesecondary cell is in a non-dormant state, the downlink control channelon the secondary cell.
 5. The method of claim 1, further comprising:detecting, while the secondary cell is in a non-dormant state, one ormore first beam failure instances (BFIs); and detecting, while thesecondary cell is in the dormant state, one or more second BFIs, andwherein the performing the BFR procedure is based on the one or morefirst BFIs and the one or more second BFIs.
 6. The method of claim 1,further comprising: detecting, while the secondary cell is in thedormant state, one or more beam failure instances (BFIs), and whereinthe performing the BFR procedure is based on a quantity of the one ormore BFIs satisfying a threshold.
 7. The method of claim 1, furthercomprising: sending, while the secondary cell is in a non-dormant stateand based on a beam failure of the secondary cell, a BFR request, andwherein performing the BFR procedure comprises receiving a BFR responseto the BFR request.
 8. A wireless device comprising: one or moreprocessors; and memory storing instructions that, when executed by theone or more processors, cause the wireless device to: receive beamfailure recovery (BFR) configuration parameters of a secondary cell;stop, during a time period in which the secondary cell is in a dormantstate, monitoring of a downlink control channel on the secondary cell;and perform, during the time period in which the secondary cell is inthe dormant state and the wireless device is not monitoring the downlinkcontrol channel on the secondary cell, a BFR procedure.
 9. The wirelessdevice of claim 8, wherein the instructions, when executed by the one ormore processors, further cause the wireless device to: receive downlinkcontrol information (DCI) indicating a transition, of the secondarycell, from a non-dormant state to a dormant state, and wherein theinstructions that, when executed by the one or more processors, causethe wireless device to stop monitoring of the downlink control channel,cause the wireless device to stop monitoring of the downlink controlchannel based on the DCI.
 10. The wireless device of claim 8, whereinthe instructions, when executed by the one or more processors, furthercause the wireless device to: receive a command indicating activation ofa power saving mode, and wherein the instructions that, when executed bythe one or more processors, cause the wireless device to stop monitoringof the downlink control channel, cause the wireless device to stopmonitoring of the downlink control channel based on the command.
 11. Thewireless device of claim 8, wherein the instructions, when executed bythe one or more processors, further cause the wireless device to:monitor, while the secondary cell is in a non-dormant state, thedownlink control channel on the secondary cell.
 12. The wireless deviceof claim 8, wherein the instructions, when executed by the one or moreprocessors, further cause the wireless device to: detect, while thesecondary cell is in a non-dormant state, one or more first beam failureinstances (BFIs); and detect, while the secondary cell is in the dormantstate, one or more second BFIs, and wherein the instructions that, whenexecuted by the one or more processors, cause the wireless device toperform the BFR procedure, cause the wireless device to perform the BFRprocedure based on the one or more first BFIs and the one or more secondBFIs.
 13. The wireless device of claim 8, wherein the instructions, whenexecuted by the one or more processors, further cause the wirelessdevice to: detect, while the secondary cell is in the dormant state, oneor more beam failure instances (BFIs), and wherein the instructionsthat, when executed by the one or more processors, cause the wirelessdevice to perform the BFR procedure, cause the wireless device toperform the BFR procedure based on a quantity of the one or more BFIssatisfying a threshold.
 14. The wireless device of claim 8, wherein theinstructions, when executed by the one or more processors, further causethe wireless device to: send, while the secondary cell is in anon-dormant state and based on a beam failure of the secondary cell, aBFR request, and wherein the instructions that, when executed by the oneor more processors, cause the wireless device to perform the BFRprocedure, cause the wireless device to receive a BFR response to theBFR request.
 15. A non-transitory computer-readable medium comprisinginstructions that, when executed, configure a wireless device to:receive beam failure recovery (BFR) configuration parameters of asecondary cell; stop, during a time period in which the secondary cellis in a dormant state, monitoring of a downlink control channel on thesecondary cell; and perform, during the time period in which thesecondary cell is in the dormant state and the wireless device is notmonitoring the downlink control channel on the secondary cell, a BFRprocedure.
 16. The non-transitory computer-readable medium of claim 15,wherein the instructions, when executed, further configure the wirelessdevice to: receive downlink control information (DCI) indicating atransition, of the secondary cell, from a non-dormant state to a dormantstate, and wherein the instructions that, when executed, configure thewireless device to stop monitoring of the downlink control channel,configure the wireless device to stop monitoring of the downlink controlchannel based on the DCI.
 17. The non-transitory computer-readablemedium of claim 15, wherein the instructions, when executed, furtherconfigure the wireless device to: receive a command indicatingactivation of a power saving mode; and wherein the instructions that,when executed, configure the wireless device to stop monitoring of thedownlink control channel, configure the wireless device to stopmonitoring of the downlink control channel based on the command.
 18. Thenon-transitory computer-readable medium of claim 15, wherein theinstructions, when executed, further configure the wireless device to:monitor, while the secondary cell is in a non-dormant state, thedownlink control channel on the secondary cell.
 19. The non-transitorycomputer-readable medium of claim 15, wherein the instructions, whenexecuted, further configure the wireless device to: detect, while thesecondary cell is in a non-dormant state, one or more first beam failureinstances (BFIs); and detect, while the secondary cell is in the dormantstate, one or more second BFIs, and wherein the instructions that, whenexecuted, configure the wireless device to perform the BFR procedure,configure the wireless device to perform the BFR procedure based on theone or more first BFIs and the one or more second BFIs.
 20. Thenon-transitory computer-readable medium of claim 15, wherein theinstructions, when executed, further configure the wireless device to:detect, while the secondary cell is in the dormant state, one or morebeam failure instances (BFIs), and wherein the instructions that, whenexecuted, configure the wireless device to perform the BFR procedure,configure the wireless device to perform the BFR procedure based on aquantity of the one or more BFIs satisfying a threshold.
 21. Thenon-transitory computer-readable medium of claim 15, wherein theinstructions, when executed, further configure the wireless device to:send, while the secondary cell is in a non-dormant state and based on abeam failure of the secondary cell, a BFR request, and wherein theinstructions that, when executed, configure the wireless device toperform the BFR procedure, configure the wireless device to receive aBFR response to the BFR request.